View EVAL-ADF7023-JDB1Z_1435606.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

high performance, low power, ism band fsk/gfsk/msk/gmsk transceiver ic adf7023-j rev. 0 information furnished by analog devices is believed to be accurate and reliable. however, no responsibility is assumed by analog devices for its use, nor for any infringements of patents or other rights of third parties that may result from its use. specifications subject to change without notice. no license is granted by implication or otherwise under any patent or patent rights of analog devices. trademarks and registered trademarks are the property of their respective owners. one technology way, p.o. box 9106, norwood, ma 02062-9106, u.s.a. tel: 781.329.4700 www.analog.com fax: 781.461.3113 ?2011 analog devices, inc. all rights reserved. features ultralow power, high performance transceiver frequency bands: 902 mhz to 958 mhz data rates supported: 1 kbps to 300 kbps 2.2 v to 3.6 v power supply single-ended and differential power amplifiers (pas) low if receiver with programmable if bandwidths 100 khz, 150 khz, 200 khz, 300 khz receiver sensitivity (ber) ?116 dbm at 1.0 kbps, 2fsk, gfsk ?107.5 dbm at 38.4 kbps, 2fsk, gfsk ?106.5 dbm at 50 kbps, 2fsk, gfsk ?105 dbm at 100 kbps, 2fsk, gfsk ?104 dbm at 150 kbps, gfsk, gmsk ?103 dbm at 200 kbps, gfsk, gmsk ?100.5 dbm at 300 kbps, gfsk, gmsk very low power consumption 12.8 ma in phy_rx mode (maximum front-end gain) 11.9 ma in phy_rx mode (agc off, adc off) 24.1 ma in phy_tx mode (10 dbm output, single-ended pa) 0.75 a in phy_sleep mode (32 khz rc oscillator active) 1.28 a in phy_sleep mode (32 khz xtal oscillator active) 0.33 a in phy_sleep mode (deep sleep mode 1) rf output power of ?20 dbm to +13.5 dbm (single-ended pa) rf output power of ?20 dbm to +10 dbm (differential pa) patented fast settling automatic frequency control (afc) digital received signal strength indication (rssi) integrated pll loop filter and tx/rx switch fast automatic voltage controlled oscillator (vco) calibration automatic synthesizer bandwidth optimization on-chip, low power, custom 8-bit processor radio control packet management smart wake mode sport mode support high speed synchronous serial interface to tx and rx data for direct interfacing to processors and dsps packet management support highly flexible for a wide range of packet formats insertion/detection of preamble/sync word/crc/address manchester and 8b/10b data encoding and decoding data whitening smart wake mode current saving low power mode with autonomous receiver wake up, carrier sense, and packet reception downloadable firmware modules image rejection calibration, fully automated (patent pending) 128-bit aes encryption/decryption with hardware acceleration and key sizes of 128 bits, 192 bits, and 256 bits reed-solomon error correction with hardware acceleration 240-byte packet buffer for tx/rx data efficient spi control interface with block read/write access integrated battery alarm and temperature sensor integrated rc and 32.768 khz crystal oscillator on-chip, 8-bit adc 5 mm 5 mm, 32-lead, lfcsp package applications smart metering ieee 802.15.4g home automation process and building control wireless sensor networks (wsns) wireless healthcare
adf7023-j rev. 0 | page 2 of 100 table of contents features .............................................................................................. 1 ? applications....................................................................................... 1 ? revision history ............................................................................... 3 ? functional block diagram .............................................................. 4 ? general description ......................................................................... 4 ? specifications..................................................................................... 6 ? rf and synthesizer specifications.............................................. 6 ? transmitter specifications........................................................... 7 ? receiver specifications ................................................................ 9 ? timing and digital specifications............................................ 12 ? auxilary block specifications ................................................... 13 ? general specifications ............................................................... 14 ? timing specifications ................................................................ 15 ? absolute maximum ratings.......................................................... 16 ? esd caution................................................................................ 16 ? pin configuration and function descriptions........................... 17 ? typical performance characteristics ........................................... 19 ? terminology .................................................................................... 26 ? radio control.................................................................................. 27 ? radio states ................................................................................. 27 ? initialization ................................................................................ 29 ? commands .................................................................................. 30 ? automatic state transitions ...................................................... 32 ? state transition and command timing.................................. 33 ? sport mode ...................................................................................... 35 ? packet structure in sport mode ............................................... 35 ? sport mode in transmit ............................................................ 35 ? sport mode in receive............................................................... 35 ? transmit bit latencies in sport mode ..................................... 35 ? packet mode .................................................................................... 38 ? preamble ...................................................................................... 38 ? sync word ................................................................................... 39 ? payload......................................................................................... 40 ? crc .............................................................................................. 41 ? postamble..................................................................................... 42 ? transmit packet timing ............................................................ 42 ? data whitening .......................................................................... 43 ? manchester encoding ................................................................ 43 ? 8b/10b encoding ........................................................................ 43 ? interrupt generation...................................................................... 44 ? interrupts in sport mode .......................................................... 46 ? adf7023-j memory map ............................................................. 47 ? bbram........................................................................................ 47 ? modem configuration ram (mcr) ...................................... 47 ? program rom ............................................................................ 47 ? program ram ............................................................................ 47 ? packet ram ................................................................................ 48 ? spi interface .................................................................................... 49 ? general characteristics ............................................................. 49 ? command access....................................................................... 49 ? status word ................................................................................. 49 ? command queuing ................................................................... 50 ? memory access........................................................................... 51 ? low power modes .......................................................................... 54 ? example low power modes...................................................... 57 ? low power mode timing diagrams........................................ 59 ? wuc setup ................................................................................. 60 ? firmware timer setup............................................................... 61 ? downloadable firmware modules............................................... 62 ? writing a module to program ram........................................ 62 ? image rejection calibration module ...................................... 62 ? aes encryption and decryption module............................... 62 ? reed-solomon coding module ............................................... 62 ? radio blocks.................................................................................... 64 ? frequency synthesizer ............................................................... 64 ? crystal oscillator........................................................................ 65 ? modulation.................................................................................. 65 ? rf output stage.......................................................................... 66 ? pa/lna interface....................................................................... 66 ? receive channel filter............................................................... 66 ? image channel rejection .......................................................... 66 ? automatic gain control (agc)............................................... 66 ? rssi .............................................................................................. 67 ? 2fsk/gfsk/msk/gmsk demodulation............................... 69 ? clock recovery........................................................................... 71 ? recommended receiver settings for 2fsk/gfsk/msk/gmsk ......................................................... 71 ? peripheral features......................................................................... 73 ? analog-to-digital converter .................................................... 73 ? temperature sensor ................................................................... 73 ?
adf7023-j rev. 0 | page 3 of 100 test dac ......................................................................................73 ? transmit test modes ..................................................................73 ? silicon revision readback .........................................................73 ? applications information...............................................................74 ? application circuit .....................................................................74 ? host processor interface ............................................................74 ? pa/lna matching ......................................................................75 ? command reference ......................................................................77 ? register maps ..................................................................................78 ? bbram register description ...................................................80 ? mcr register description.........................................................90 ? packet ram register description............................................97 ? outline dimensions........................................................................98 ? ordering guide ...........................................................................98 ? revision history 5 /11revision 0: initial version
adf7023-j rev. 0 | page 4 of 100 functional block diagram rssi/ logamp lna adcin_atb3 sclk mosi 1 gpio refers to pins 17, 18, 19, 20, 25, and 27. miso cs irq_gp3 rfio_1p rfio_1n rfo2 spi irq ctrl fsk ask demod cdr afc agc 4kb rom mac 256 byte packet ram 2kb ram 8-bit risc processor bias 26mhz osc ldo4 ldo3 ldo2 ldo1 wake-up control timer unit 64 byte bbram temp sensor battery monitor clock divider gpio test dac analog test pa ramp profile pa mux 8-bit adc loop filter charge pump pfd 26mhz osc divider - ? modulator gaussian filter f dev 32khz rcosc 32khz osc pa adf7023-j 256 byte mcr ram gpio 1 divider xosc26n xosc26p xosc32kp_gp5_atb1 xosc32kn_atb2 rbias cregrfx cregvco cregsynth cregdigx 09555-001 figure 1. general description the adf7023-j is a very low power, high performance, highly integrated 2fsk/gfsk/msk/gmsk transceiver designed for operation in the 902 mhz to 958 mhz frequency band, which covers the arib standard t96 band at 950 mhz. data rates from 1 kbps to 300 kbps are supported. the transmit rf synthesizer contains a vco and a low noise fractional-n phase locked loop (pll) with an output channel frequency resolution of 400 hz. the vco operates at twice the fundamental frequency to reduce spurious emissions. the receive and transmit synthesizer bandwidths are automatically, and independently, configured to achieve optimum phase noise, modulation quality, and settling time. the transmitter output power is programmable from ?20 dbm to +13.5 dbm, with automatic pa ramping to meet transient spurious specifications. the part possesses both single-ended and differential pas, which allow for tx antenna diversity. the receiver is exceptionally linear, achieving an ip3 specification of ?12.2 dbm and ?11.5 dbm at maximum gain and minimum gain, respectively, and an ip2 specification of 18.5 dbm and 27 dbm at maximum gain and minimum gain, respectively. the receiver achieves an interference blocking specification of 66 db at a 2 mhz offset and 74 db at a 10 mhz offset. thus, the part is extremely resilient to the presence of interferers in spectrally noisy environments. the receiver features a novel, high speed, afc loop, allowing the pll to find and correct any rf frequency errors in the recovered packet. a patent pending image rejection calibration scheme is available by downloading the image rejection calibration firmware module to program ram. the algorithm does not require the use of an external rf source nor does it require any user intervention once initiated. the results of the calibration can be stored in nonvolatile memory for use on subsequent power-ups of the transceiver. the adf7023-j operates with a power supply range of 2.2 v to 3.6 v and has very low power consumption in both tx and rx modes, enabling long lifetimes in battery-operated systems while maintaining excellent rf performance. the device can enter a low power sleep mode in which the configuration settings are retained in the battery backup random access memory (bbram). the adf7023-j features an ultralow power, on-chip, communications processor. the communications processor, which is an 8-bit risc processor, performs the radio control, packet management, and smart wake mode (swm) functionality. the communications processor eases the processing burden of the companion processor by integrating the lower layers of a typical communication protocol stack. the communications processor also permits the download and execution of firmware modules. available modules include image rejection (ir) calibration, advanced encryption standard (aes) encryption, and reed-solomon coding. these firmware modules are included in the applications software, which is available online at ftp://ftp.analog.com/pub/rfl/adf7023/ . the communications processor provides a simple command-based radio control interface for the host processor. a single-byte command transitions the radio between states or performs a radio function. the communications processor provides support for generic packet formats. the packet format is highly flexible and fully programmable, thereby ensuring its compatibility with proprietary packet profiles. in transmit mode, the communications processor can be configured to add preamble, sync word, and crc to the
adf7023-j rev. 0 | page 5 of 100 payload data stored in packet ram. in receive mode, the communications processor can detect and interrupt the host processor on reception of preamble, sync word, address, and crc and store the received payload to packet ram. the adf7023-j uses an efficient interrupt system comprising mac level interrupts and phy level interrupts that can be individually set. the payload data plus the 16-bit crc can be encoded/decoded using manchester or 8b/10b encoding. alternatively, data whitening and dewhitening can be applied. the swm allows the adf7023-j to wake up autonomously from sleep using the internal wake-up timer without intervention from the host processor. after wake-up, the adf7023-j is controlled by the communications processor. this functionality allows carrier sense, packet sniffing, and packet reception while the host processor is in sleep, thereby reducing overall system current consumption. the smart wake mode can wake the host processor on an interrupt condition. these interrupt conditions can be configured to include the reception of valid preamble, sync word, crc, or address match. wake-up from sleep mode can also be triggered by the host processor. for systems requiring very accurate wake-up timing, a 32 khz oscillator can be used to drive the wake-up timer. alternatively, the internal rc oscillator can be used, which gives lower current consumption in sleep. the adf7023-j features an aes engine with hardware acceleration that provides 128-bit block encryption and decryption with key sizes of 128 bits, 192 bits, and 256 bits. both electronic code book (ecb) and cipher block chaining mode 1 (cbc mode 1) are supported. the aes engine can be used to encrypt/decrypt packet data and can be used as a stand- alone engine for encryption/decryption by the host processor. the aes engine is enabled on the adf7023-j by downloading the aes firmware module to program ram. an on-chip, 8-bit adc provides readback of an external analog input, the rssi signal, or an integrated temperature sensor. an integrated battery voltage monitor raises an interrupt flag to the host processor whenever the battery voltage drops below a user- defined threshold.
adf7023-j rev. 0 | page 6 of 100 specifications v dd = vddbat1 = vddbat2 = 2.2 v to 3.6 v, gnd = 0 v, t a = t min to t max , unless otherwise noted. typical specifications are at v dd = 3 v and t a = 25c. rf and synthesizer specifications table 1. parameter min typ max unit test conditions/comments rf characteristics frequency range 902 958 mhz phase-locked loop channel frequency resolution 396.7 hz phase noise at offset of pa output power = 10 dbm, rf frequency = 950 mhz 600 khz ?116.3 dbc/hz 130 khz closed-loop bandwidth 1 800 khz ?119.4 dbc/hz 130 khz closed-loop bandwidth 600 khz ?113.8 dbc/hz 223 khz closed-loop bandwidth 2 800 khz ?117.2 dbc/hz 223 khz closed-loop bandwidth 1 mhz ?126 dbc/hz 2 mhz ?131 dbc/hz 10 mhz ?142 dbc/hz vco calibration time 142 s synthesizer settling time 56 s frequency synthesizer settles to within 5 ppm of the target frequency within this time following the vco calibration, transmit, and receive, 2fsk/gfsk/msk/gmsk integer boundary spurious 3 n = 35 or 36 (26 mhz n) + 0.1 mhz ?39 dbc using 130 khz synthesizer bandwidth, integer boundary spur at 910 mhz (26 mhz 35), inside synthesizer loop bandwidth (26 mhz n) + 1.0 mhz ?79 dbc using 130 khz synthesizer bandwidth, integer boundary spur at 910 mhz (26 mhz 35), outside synthesizer loop bandwidth crystal oscillator crystal frequency 26 mhz parallel load resonant crystal recommended load capacitance 7 18 pf maximum crystal esr 1800 26 mhz crystal with 18 pf load capacitance pin capacitance 2.1 pf capacitance for xosc26p and xosc26n start-up time 310 s 26 mhz crystal with 7 pf load capacitance 388 s 26 mhz crystal with 18 pf load capacitance 1 130 khz closed -loop bandwidth reco mmended for t96/15.4 g , 50 kbps and 100 kbps da ta rates (see table 31). 2 223 khz closed -loop bandwidth reco mmended for t96/15.4 g , 200 kbps data rate (see table 31). 3 as the 26 mhz xtal is fixed, i nteger boundary spurs occur at 910 mh z and 936 mhz (n = 35 and n = 36).
adf7023-j rev. 0 | page 7 of 100 transmitter specifications table 2. parameter min typ max unit test conditions/comments data rate 2fsk/gfsk/msk/gmsk 1 300 kbps data rate resolution 100 bps modulation error ratio (mer) 1 rf frequency = 957.2 mhz, gfsk 10 kbps to 49.5 kbps 25.4 db modulation index = 1 49.6 kbps to 129.5 kbps 25.3 db modulation index = 1 129.6 kbps to 179.1 kbps 23.9 db modulation index = 0.5 179.2 kbps to 239.9 kbps 23.3 db modulation index = 0.5 240 kbps to 300 kbps 23 db modulation index = 0.5 modulation error ratio 15.4 g data rates with t96 look-up table (lut) 2 50 kbps 25.4 db modulation index = 1 100 kbps 28.9 db modulation index = 1 200 kbps 25.9 db modulation index = 1 100 kbps 24.3 db modulation index = 0.5 modulation 2fsk/gfsk/msk/gmsk frequency deviation 0.1 409.5 khz deviation frequency resolution 100 hz gaussian filter bandwidth-time (bt) product 0.5 single-ended pa maximum power 3 13.5 dbm programmable, separate pa and lna match 4 minimum power ?20 dbm transmit power variation vs. temperature 0.5 db from ?40c to +85c, rf frequency = 958.0 mhz transmit power variation vs. v dd 1 db from 2.2 v to 3.6 v, rf frequency = 958.0 mhz transmit power flatness 1 db from 902 mhz to 928 mhz and 950 mhz to 958 mhz programmable step size ?20 dbm to +13.5 dbm 0.5 db programmable in 63 steps differential pa maximum power 3 10 dbm programmable minimum power ?20 dbm transmit power variation vs. temperature 1 db from ?40c to +85c, rf frequency = 958.0 mhz transmit power variation vs. v dd 2 db from 2.2 v to 3.6 v, rf frequency = 958.0 mhz transmit power flatness 1 db from 902 mhz to 928 mhz and 950 mhz to 958 mhz programmable step size ?20 dbm to +10 dbm 0.5 db programmable in 63 steps
adf7023-j rev. 0 | page 8 of 100 parameter min typ max unit test conditions/comments spurious emissions measured as per telec t-245 for t96 compliance, 950 mhz to 958 mhz band, single-ended pa with combined output. for spurious emissions compliance in the 1.8845 ghz to 1.9196 ghz frequency band, a seventh-order pa harmonic filter is used. this has an insertion loss of up to 1.5 db. 30 mhz to 710 mhz ?65 dbm/100 khz 710 mhz to 945 mhz ?63 dbm/1 mhz 945 mhz to 950 mhz ?66 dbm/100 khz 958 mhz to 960 mhz ?60.7 dbm/100 khz dr = 100 kbps, mi = 1, n = 2, f c = 957.3 mhz 960 mhz to 1 ghz ?64 dbm/100 khz 1 ghz to 1.215 ghz ?72 dbm/1 mhz 1.215 ghz to 1.8845 ghz ?76 dbm/1 mhz 1.8845 ghz to 1.9196 ghz 5 ?69 dbm/1 mhz 1.9196 ghz to 3 ghz ?66 dbm/1 mhz 3 ghz to 5 ghz ?69 dbm/1 mhz optimum pa load impedance single-ended pa in transmit mode f rf = 915 mhz 50.8 + j10.2 f rf = 954mhz 38.5 + j5.9 single-ended pa in receive mode pa impedance in rx mode f rf = 915 mhz 9.4 ? j124 f rf = 954 mhz 8.8 ? j118.5 differential pa in transmit mode load impedance between rfio_1p and rfio_1n to ensure maximum output power f rf = 915 mhz 20.5 + j36.4 f rf = 954 mhz 28.1 + j17.3 1 mer is a measure of signal to noise ratio at optimal eye sampling point. 2 optimized pll bandwidth settings vs. data rate defined in table 31. 3 measured as the maximum unmodulated power. 4 a combined single-ended pa and lna match can reduce the maximum achievable output power by up to 1 db. 5 this includes the second harmonic.
adf7023-j rev. 0 | page 9 of 100 receiver specifications table 3. parameter min typ max unit test conditions/comments 2fsk/msk input sensitivity, bit error rate (ber) at ber = 1e ? 3, rf frequency = 915 mhz, lna and pa matched separately 1 1.0 kbps ?116 dbm frequency deviation = 4.8 khz, if filter bandwidth = 100 khz 10 kbps ?111 dbm frequency deviation = 9.6 khz, if filter bandwidth = 100 khz 38.4 kbps ?107.5 dbm frequency deviation = 20 khz, if filter bandwidth = 100 khz 50 kbps ?106.5 dbm frequency deviation = 12.5 khz, if filter bandwidth = 100 khz 100 kbps ?105 dbm frequency deviation = 25 khz, if filter bandwidth = 100 khz 150 kbps ?104 dbm frequency deviation = 37.5 khz, if filter bandwidth = 150 khz 200 kbps ?103 dbm frequency deviation = 50 khz, if filter bandwidth = 200 khz 300 kbps ?100.5 dbm frequency deviation = 75 khz, if filter bandwidth = 300 khz gfsk/gmsk input sensitivity, ber at ber = 1e ? 3, rf frequency = 954 mhz, lna and pa matched separately 1 50 kbps ?107.4 dbm frequency deviation = 25 khz, if filter bandwidth = 100 khz 100 kbps ?105 dbm frequency deviation = 50 khz, if filter bandwidth = 100 khz 100 kbps ?106 dbm frequency deviation = 40 khz, if filter bandwidth = 100 khz 200 kbps ?102 dbm frequency deviation = 100 khz, if filter bandwidth = 200 khz 200 kbps ?103.3 dbm frequency deviation = 80 khz, if filter bandwidth = 200 khz 2fsk/msk input sensitivity, packet error rate (per) at per = 1%, rf frequency = 915 mhz, lna and pa matched separately, 2 packet length = 128 bits, packet mode 1.0 kbps ?115.5 dbm frequency deviation = 4.8 khz, if filter bandwidth = 100 khz 9.6 kbps ?110.6 dbm frequency deviation = 9.6 khz, if filter bandwidth = 100 khz 38.4 kbps ?106 dbm frequency deviation = 20 khz, if filter bandwidth = 100 khz 50 kbps ?104.3 dbm frequency deviation = 12.5 khz, if filter bandwidth = 100 khz 100 kbps ?102.6 dbm frequency deviation = 25 khz, if filter bandwidth = 100 khz 150 kbps ?101 dbm frequency deviation = 37.5 khz, if filter bandwidth = 150 khz 200 kbps ?99.1 dbm frequency deviation = 50 khz, if filter bandwidth = 200 khz 300 kbps ?97.9 dbm frequency deviation = 75 khz, if filter bandwidth = 300 khz
adf7023-j rev. 0 | page 10 of 100 parameter min typ max unit test conditions/comments gfsk/gmsk input sensitivity, per at per = 1%, rf frequency = 954 mhz, lna and pa matched separately, packet length = 20 octets, packet mode 50 kbps ?104.1 dbm frequency deviation = 25 khz, if filter bandwidth = 100 khz 100 kbps ?101.1 dbm frequency deviation = 50 khz, if filter bandwidth = 100 khz 100 kbps ?102.2 dbm frequency deviation = 40 khz, if filter bandwidth = 100 khz 200 kbps ?98.5 dbm frequency deviation = 100 khz, if filter bandwidth = 200 khz 200 kbps ?99.5 dbm frequency deviation = 80 khz, if filter bandwidth = 200 khz lna and mixer, input ip3 receiver lo frequency (f lo ) = 914.8 mhz, f source1 = f lo + 0.4 mhz, f source2 = f lo + 0.7 mhz minimum lna gain ?11.5 dbm maximum lna gain ?12.2 dbm lna and mixer, input ip2 receiver lo frequency (f lo ) = 920.8 mhz, f source1 = f lo + 1.1 mhz, f source2 = f lo + 1.3 mhz maximum lna gain, maximum mixer gain 18.5 dbm minimum lna gain, minimum mixer gain 27 dbm lna and mixer, 1 db compression point rf frequency = 915 mhz maximum lna gain, maximum mixer gain ?21.9 dbm minimum lna gain, minimum mixer gain ?21 dbm adjacent channel rejection cw interferer desired signal at ?87 dbm, cw interferer power level increased until ber = 62 ?6 , image calibrated 200 khz offset 38 db if bw = 100 khz, wanted signal: f dev = 25 khz, dr = 50 kbps +400 khz offset 51 db ?400 khz offset 33/39 db uncalibrated/internal calibration; using an if of 200 khz, ?400 khz is the image frequency co-channel rejection ?6 db desired signal at ?87 dbm, data rate = 50 kbps, frequency deviation = 25 khz, rf frequency = 954 mhz blocking rf frequency = 954 mhz desired signal 3 db above the input sensitivity level, data rate = 50 kbps, cw interferer power level increased until ber = 10 ?3 (see the typical performance characteristics section for blocking at other offsets and if bandwidths), image calibrated 2 mhz 65 db 10 mhz 72 db 60 mhz 76 db image channel attenuation measured as image attenuation at the if filter output, carrier wave interferer at 400 khz below the channel frequency, 100 khz if filter bandwidth 954 mhz 36/43.8 db uncalibrated/calibrated
adf7023-j rev. 0 | page 11 of 100 parameter min typ max unit test conditions/comments afc accuracy 1 khz maximum pull-in range achievable pull-in range dependent on discriminator bandwidth and modulation 300 khz if filter bandwidth 150 khz 200 khz if filter bandwidth 100 khz 150 khz if filter bandwidth 75 khz 100 khz if filter bandwidth 50 khz preamble length minimum number of preamble bits to ensure the minimum per across the full input power range (see table 41 ) afc off, agc lock on sync word detection sync word length 24 bits 38.4 kbps 8 bits sync word tolerance = 0 300 kbps 24 bits sync word tolerance = 1 afc on, afc and agc lock on preamble detection 9.6 kbps 46 bits 38.4 kbps 44 bits 50 kbps 50 bits 100 kbps 52 bits 150 kbps 54 bits 200 kbps 58 bits 300 kbps 64 bits afc on, afc and agc lock on sync word detection sync word length 24 bits 38.4 kbps 14 bits sync word tolerance = 0 300 kbps 32 bits sync word tolerance = 1 rssi range at input ?97 to ?26 dbm linearity 2 db absolute accuracy 3 db saturation (maximum input level) 2fsk/gfsk/msk/gmsk 12 dbm lna input impedance receive mode f rf = 915 mhz 75.9 ? j32.3 f rf = 954 mhz 74.6 ? j32.5 transmit mode f rf = 915 mhz 7.7 + j8.6 f rf = 954 mhz 7.7 + j8.9 rx spurious emissions 2 maximum < 1 ghz ?66 dbm at antenna input, unfiltered conductive maximum > 1 ghz ?62 dbm at antenna input, unfiltered conductive 1 sensitivity for combined matching network case is typically 1 db less than separate matching networks. 2 follow the matching and la yout guidelines to achieve the releva nt arib-t96/telec t-245 specifications.
adf7023-j-j rev. 0 | page 12 of 100 timing and digital specifications table 4. parameter min typ max unit test conditions/comments rx and tx timing parameters see the state transition and command timing section for more details phy_on to phy_rx (on cmd_phy_rx) 300 s includes vco calibration and synthesizer settling phy_on to phy_tx (on cmd_phy_tx) 296 s includes vco calibration and synthesizer settling, does not include pa ramp-up logic inputs input high voltage, v inh 0.7 v dd v input low voltage, v inl 0.2 v dd v input current, i inh /i inl 1 a input capacitance, c in 10 pf logic outputs output high voltage, v oh v dd ? 0.4 v i oh = 500 a output low voltage, v ol 0.4 v i ol = 500 a gpio rise/fall 5 ns gpio load 10 pf maximum output current 5 ma atb outputs used for external pa and lna control adcin_atb3 and atb4 output high voltage, v oh 1.8 v output low voltage, v ol 0.1 v maximum output current 0.5 ma xosc32kp_gp5_atb1 and xosc32kn_atb2 output high voltage, v oh v dd v output low voltage, v ol 0.1 v maximum output current 5 ma
adf7023-j rev. 0 | page 13 of 100 auxilary block specifications table 5. parameter min typ max unit test conditions/comments 32 khz rc oscillator frequency 32.768 khz after calibration frequency accuracy 1.5 % after calibration at 25c frequency drift temperature coefficient 0.14 %/c voltage coefficient 4 %/v calibration time 1 ms 32 khz xtal oscillator frequency 32.768 khz start-up time 630 ms 32.768 khz crystal with 7 pf load capacitance wake up controller (wuc) hardware timer wake-up period 61 10 ?6 1.31 10 5 sec firmware timer wake-up period 1 2 16 hardware periods firmware counter counts of the number of hardware wake-ups, resolution of 16 bits adc resolution 8 bits dnl 1 lsb from 2.2 v to 3.6 v, t a = 25c inl 1 lsb from 2.2 v to 3.6 v, t a = 25c conversion time 1 s input capacitance 12.4 pf battery monitor absolute accuracy 45 mv alarm voltage setpoint 1.7 2.7 v alarm voltage step size 62 mv 5-bit resolution start-up time 100 s current consumption 30 a when enabled temperature sensor range ?40 +85 c resolution 0.3 c with averaging accuracy of single temperature readback +7/?4 c overtemperature range ?40c to +85c (calibrated at +25c) 4 c overtemperature range ?36c to +84c (calibrated at +25c) 3 c overtemperature range ?12c to +79c (calibrated at +25c)
adf7023-j rev. 0 | page 14 of 100 general specifications table 6. parameter min typ max unit test conditions/comments temperature range, t a ?40 +85 c voltage supply v dd 2.2 3.6 v applied to vddbat1 and vddbat2 transmit current consumption in the phy_tx state, single-ended pa matched to 50 , differential pa matched to 100 , separate single-ended pa and lna match, combined differential pa and lna match single-ended pa, 915 mhz ?10 dbm 10.3 ma 0 dbm 13.3 ma 10 dbm 24.1 ma 13.5 dbm 32.1 ma differential pa, 915 mhz ?10 dbm 9.3 ma 0 dbm 12 ma 5 dbm 16.7 ma 10 dbm 28 ma power modes phy_sleep (deep sleep mode 2) 0.18 a sleep mode, wake-up configuration values (bbram) not retained phy_sleep (deep sleep mode 1) 0.33 a sleep mode, wake-up configuration values (bbram) retained phy_sleep (rco wake mode) 0.75 a wuc active, rc oscillator running, wake-up configuration values retained (bbram) phy_sleep (xto wake mode) 1.28 a wuc active, 32 khz crystal running, wake-up configuration values retained (bbram) phy_off 1 ma device in phy_off state, 26 mhz oscillator running, digital and synthesizer regulators active, all register values retained phy_on 1 ma device in phy_on state, 26 mhz oscillator running, digital, synthesizer, vco, and rf regulators active, baseband filter calibration performed, all register values retained phy_rx (adc, agc off ) 11.9 ma device in phy_rx state, adc off, manual agc gain phy_rx (adc, agc on) 12.8 ma device in phy_rx state smart wake mode average current consumption 21.78 a autonomous reception every 1 sec, with receive dwell time of 1.25 ms, using rc oscillator, data rate = 38.4 kbps 11.75 a autonomous reception every 1 sec, with receive dwell time of 0.5 ms, using rc oscillator, data rate = 300 kbps
adf7023-j rev. 0 | page 15 of 100 timing specifications v dd = vddbat1 = vddbat2 = 3 v 10%, v gnd = gnd = 0 v, t a = t min to t max , unless otherwise noted. table 7. spi interface timing parameter limit unit test conditions/comments t 1 15 ns max cs falling edge to miso setup time (trx active) t 2 85 ns min cs low to sclk setup time t 3 85 ns min sclk high time t 4 85 ns min sclk low time t 5 170 ns min sclk period t 6 10 ns max sclk falling edge to miso delay t 7 5 ns min mosi to sclk rising edge setup time t 8 5 ns min mosi to sclk rising edge hold time t 9 85 ns min sclk falling edge to cs hold time t 11 270 ns min cs high time t 12 310 s typ cs low to miso high wake-up time, 26 mhz crystal with 7 pf load capacitance, t a = 25c t 13 20 ns max sclk rise time t 14 20 ns max sclk fall time timing diagrams t 11 t 9 t 4 t 5 t 13 t 3 t 2 t 14 t 1 t 6 t 8 t 7 cs s clk miso mosi 7 7 65432107 bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 bit 7 bit 0 x bit 7 09555-002 figure 2. spi interface timing spi state cs sclk miso sleep wake up spi ready x 012345 t 9 67 t 6 t 1 t 12 09555-003 figure 3. phy_sleep to spi ready state timing (spi ready t12 after falling edge of cs )
adf7023-j rev. 0 | page 16 of 100 absolute maximum ratings t a = 25c, unless otherwise noted. connect the exposed paddle of the lfcsp package to ground. table 8. parameter rating vddbat1, vddbat2 to gnd ?0.3 v to +3.96 v operating temperature range industrial ?40c to +85c storage temperature range ?65c to +125c maximum junction temperature 150c lfcsp ja thermal impedance 26c/w reflow soldering peak temperature 260c time at peak temperature 40 sec stresses above those listed under absolute maximum ratings may cause permanent damage to the device. this is a stress rating only; functional operation of the device at these or any other conditions above those indicated in the operational section of this specification is not implied. exposure to absolute maximum rating conditions for extended periods may affect device reliability. this device is a high performance, rf integrated circuit with an esd rating of <2 kv; it is esd sensitive. take proper precautions for handling and assembly. esd caution
adf7023-j rev. 0 | page 17 of 100 pin configuration and fu nction descriptions notes 1. nc = no connect. do not connect to this pin. 2 . connect exposed pad to gnd. 24 cs 23 mosi 22 sclk 21 miso 20 irq_gp3 19 gp2 18 gp1 17 gp0 1 2 3 4 5 6 7 8 cregrf1 rbias cregrf2 rfio_1p rfio_1n rfo2 vddbat2 nc 9 10 11 12 13 14 15 16 cregvco vcoguard cregsynth cwakeup xosc26p xosc26n dguard cregdig1 32 31 30 29 28 27 26 25 adcvref atb4 adcin_atb3 vddbat1 xosc32kn_atb2 xosc32kp_gp5_atb1 cregdig2 gp4 top view (not to scale) adf7023-j epad 09555-004 figure 4. pin configuration table 9. pin function descriptions pin no. mnemonic description 1 cregrf1 regulator voltage for rf. a 220 nf capacitor should be placed between this pin and ground for regulator stability and noise rejection. 2 rbias external bias resistor. a 36 k resistor with 2% tolerance should be used. 3 cregrf2 regulator voltage for rf. a 220 nf capacitor should be placed between this pin and ground for regulator stability and noise rejection. 4 rfio_1p lna positive input in receive mode. pa pos itive output in transmit mo de with differential pa. 5 rfio_1n lna negative input in receive mode. pa nega tive output in transmit mo de with differential pa. 6 rfo2 single-ended pa output. 7 vddbat2 power supply pin two. decoupling capacitors to the ground plane should be placed as close as possible to this pin. 8 nc no connect. 9 cregvco regulator voltage for the vco. a 220 nf capacitor sh ould be placed between this pin and ground for regulator stability and noise rejection. 10 vcoguard guard/screen for vco. this pin should be connected to pin 9. 11 cregsynth regulator voltage for the synthesizer. a 220 nf capacitor should be placed between this pin and ground for regulator stability and noise rejection. 12 cwakeup external capacitor for wake-up control. a 150 nf ca pacitor should be placed between this pin and ground. 13 xosc26p the 26 mhz reference crystal should be connected between this pin and xosc26n. 14 xosc26n the 26 mhz reference crystal should be connected between this pin and xosc26p. 15 dguard internal guard/screen for the digital circuitry. a 220 nf capacitor should be placed between this pin and ground. 16 cregdig1 regulator voltage for digital section of the chip. a 220 nf capacitor should be placed between this pin and ground for regulator stability and noise reje ction. this can be achieved by shorting it to pin 15 and sharing the capacitor to ground. 17 gp0 digital gpio pin 0. 18 gp1 digital gpio pin 1. 19 gp2 digital gpio pin 2. 20 irq_gp3 interrupt request, digital gpio test pin 3. an rc filter should be placed between this pin and the host processor. recommended values are r = 1.1 k and c = 1.5 nf.
adf7023-j rev. 0 | page 18 of 100 pin no. mnemonic description 21 miso serial port master in/slave out. 22 sclk serial port clock. 23 mosi serial port master out/slave in. 24 cs chip select (active low). a pull-up resistor of 100 k to v dd is recommended to prevent the host processor from inadvertently waking the adf7023-j from sleep. 25 gp4 digital gpio test pin 4. 26 cregdig2 regulator voltage for digital section of the chip. a 220 nf capacitor should be placed between this pin and ground for regulator stability and noise rejection. 27 xosc32kp_gp5_atb1 digital gpio test pin 5. a 32 khz watch crystal can be connected between this pin and xosc32kn_atb2. analog test pin 1. 28 xosc32kn_atb2 a 32 khz watch crystal can be connected between this pin and xosc32kp_gp5_atb1. analog test pin 2. 29 vddbat1 digital power supply pin one. decoup ling capacitors to the ground plane should be placed as close as possible to this pin. 30 adcin_atb3 analog-to-digital converter input. can be configured as an external pa enable signal. analog test pin 3. 31 atb4 analog test pin 4. can be configured as an external lna enable signal. 32 adcvref adc reference output. a 220 nf capacitor should be placed between this pin and ground for adequate noise rejection. epad the exposed package paddle must be connected to gnd.
adf7023-j rev. 0 | page 19 of 100 typical performance characteristics ?20 ?18 ?16 ?14 ?12 ?10 ?8 ?6 ?4 ?2 0 2 4 6 8 10 12 14 0 4 8 12 16 20 24 28 32 36 40 44 48 52 56 60 64 output power (dbm) pa setting ?40c, 3.6v ?40c, 3.0v ?40c, 2.4v ?40c, 1.8v +85c, 3.6v +85c, 3.0v +85c, 2.4v +85c, 1.8v +25c, 3.6v +25c, 3.0v +25c, 2.4v +25c, 1.8v 09555-205 6 8 10 12 14 16 18 20 22 24 26 28 30 32 ?18 ?16 ?14 ?12 ?10 ?8 ?6 ?4 ?2 0 2 4 6 8 10 12 supply current (ma) output power (dbm) ?40c, 3.6v ?40c, 1.8v +85c, 3.6v +85c, 1.8v 09555-210 figure 8. differential pa at 915 mhz: supply current vs. output power, temperature, and v dd (minimum recommended v dd = 2.2 v, 1.8 v operation shown for robustness) figure 5. single-ended pa at 915 mhz: output power vs. pa_level_mcr setting, temperature, and v dd (minimum recommended v dd = 2.2 v, 1.8 v operation shown for robustness) ?60 ?50 ?40 ?30 ?20 ?10 0 10 0 50 100 150 200 250 300 350 400 450 500 pa output power (dbm) time (s) pa ramp = 1 pa ramp = 2 pa ramp = 3 pa ramp = 4 pa ramp = 5 pa ramp = 6 pa ramp = 7 09555-211 6 8 10 12 14 16 18 20 22 24 26 28 30 32 34 36 ?18 ?16 ?14 ?12 ?10 ?8 ?6 ?4 ?2 0 2 4 6 8 10 12 14 supply current (ma) output power (dbm) ?40c, 3.6v ?40c, 1.8v +85c, 3.6v +85c, 1.8v 09555-206 figure 9. pa ramp-up at data rate = 38.4 kbps for each pa_ramp setting, differential pa figure 6. single-ended pa at 915 mhz: supply current vs. output power, temperature, and v dd (minimum recommended v dd = 2.2 v, 1.8 v operation shown for robustness) ?60 ?50 ?40 ?30 ?20 ?10 0 10 0 50 100 150 200 250 300 350 400 450 500 pa output power (dbm) time (s) pa ramp = 1 pa ramp = 2 pa ramp = 3 pa ramp = 4 pa ramp = 5 pa ramp = 6 pa ramp = 7 09555-212 ?20 ?18 ?16 ?14 ?12 ?10 ?8 ?6 ?4 ?2 0 2 4 6 8 10 12 0 4 8 1216202428323640444852566064 output power (dbm) pa level setting ?40c, 3.6v ?40c, 3.0v ?40c, 2.4v ?40c, 1.8v +85c, 3.6v +85c, 3.0v +85c, 2.4v +85c, 1.8v +25c, 3.6v +25c, 3.0v +25c, 2.4v +25c, 1.8v 09555-209 figure 10. pa ramp-down at data rate = 38.4 kbps for each pa_ramp setting, differential pa figure 7. differential pa at 915 mhz: output power vs. pa_level_mcr setting, temperature, and v dd (minimum recommended v dd = 2.2 v, 1.8 v operation shown for robustness)
adf7023-j rev. 0 | page 20 of 100 ?60 ?50 ?40 ?30 ?20 ?10 0 10 0 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 pa output power (dbm) time (s) pa ramp = 4 pa ramp = 5 pa ramp = 6 pa ramp = 7 09555-213 figure 11. pa ramp-up at da ta rate = 300 kbps for each pa_ramp setting, differential pa ?60 ?50 ?40 ?30 ?20 ?10 0 10 0 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 pa output power (dbm) time (s) pa ramp = 4 pa ramp = 5 pa ramp = 6 pa ramp = 7 09555-214 figure 12. pa ramp-down at data rate = 300 kbps for each pa_ramp setting, differential pa ?45 ?40 ?35 ?30 ?25 ?20 ?15 ?10 ?5 0 5 10 15 ?1000 ?900 ?800 ?700 ?600 ?500 ?400 ?300 ?200 ?100 0 100 200 300 400 500 600 700 800 900 1000 power (dbm) frequency offset (khz) 3.6v, +25c 1.8v, +85c 3.6v, ?40c 1.8v, ?40c 3.6v, +85c 1.8v, +25c 09555-217 figure 13. transmit spectrum at 928 mhz, gfsk, data rate = 300 kbps, frequency deviation = 75 khz (minimum recommended v dd = 2.2 v, 1.8 v operation shown for robustness) ?40 ?35 ?30 ?25 ?20 ?15 ?10 ?5 0 5 ?40 ?35 ?30 ?25 ?20 ?15 mixer output power (dbm) lna input power (dbm) output power (fundamental) output power ideal p1db p1db = ?21dbm 09555-225 figure 14. lna/mixer 1 db compression point, v dd = 3.0 v, temperature = 25c, rf frequency = 915 mhz, lna gain = low, mixer gain = low output power (fundamental) output power ideal p1db ?10 ?5 0 5 10 15 20 ?40 ?35 ?30 ?25 ?20 ?15 mixer output power (dbm) lna input power (dbm) p1db = ?21.9dbm 09555-226 figure 15. lna/mixer 1 db compression point, v dd = 3.0 v, temperature = 25c, rf frequency = 915 mhz, lna gain = high, mixer gain = high ?130 ?120 ?110 ?100 ?90 ?80 ?70 ?60 ?50 ?40 ?30 ?20 ?10 0 10 ?50 ?45 ?40 ?35 ?30 ?25 ?20 ?15 ?10 mixer output power (dbm) lna input power (dbm) fundamental tone im3 tone fundamental 1/1 slope fit im3 3/1 slope fit iip3 = ?11.5dbm 09555-227 figure 16. lna/mixer iip3, v dd = 3.0 v, temperature = 25c, rf frequency = 915 mhz, lna gain = low, mixer gain = low, source 1 frequency = (915 + 0.4) mhz, source 2 frequency = (915+ 0.7) mhz
adf7023-j rev. 0 | page 21 of 100 ?90 ?80 ?70 ?60 ?50 ?40 ?30 ?20 ?10 0 10 20 ?50 ?45 ?40 ?35 ?30 ?25 ?20 ?15 ?10 mixer output power (dbm) lna input power (dbm) iip3 = ?12.2dbm fundamental tone im3 tone fundamental 1/1 slope fit im3 3/1 slope fit 09555-228 figure 17. lna/mixer iip3, v dd = 3.0 v, temperature = 25c, rf frequency = 915 mhz, lna gain = high, mixer gain = high, source 1 frequency = (915 + 0.4) mhz, source 2 frequency = (915+ 0.7) mhz ?90 ?80 ?70 ?60 ?50 ?40 ?30 ?20 ?10 0 10 0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 attenuation (db) frequency offset (mhz) 100khz 150khz 200khz 300khz 09555-229 figure 18. if filter prof ile vs. if bandwidth, v dd = 3.0 v, temperature = 25c ?90 ?80 ?70 ?60 ?50 ?40 ?30 ?20 ?10 0 10 0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 attenuation (db) frequency offset (mhz) 3.6v, +85c 1.8v, ?40c 2.4v, ?40c 3.0v, ?40c 3.6v, ?40c 1.8v, +25c 2.4v, +25c 3.0v, +25c 3.6v, +25c 1.8v, +85c 2.4v, +85c 3.0v, +85c 09555-230 figure 19. if filter profile vs. v dd and temperature, 100 khz if filter bandwidth ?10 0 10 20 30 40 50 60 70 80 ?11 ?10 ?9 ?8 ?7 ?6 ?5 ?4 ?3 ?2 ?1 0 1 2 3 4 5 6 7 8 9 10 11 blocking (db) modulated interferer carrier wave interferer interferer offset from receiver lo frequency (mhz) 09555-237 figure 20. receiver wideband blocking at 915 mhz, data rate = 38.4 kbps ?20 ?10 0 10 20 30 40 50 60 70 80 ?10 ?9 ?8 ?7 ?6 ?5 ?4 ?3 ?2 ?1 0 1 2 3 4 5 6 7 8 9 10 blocking (db) interferer offset from receiver lo frequency (mhz) modulated interferer carrier wave interferer 09555-238 figure 21. receiver wideband blocking at 915 mhz, data rate = 100 kbps interferer offset from receiver lo frequency (mhz) ?10 ?20 0 10 20 30 40 50 60 70 ?11 ?10 ?9 ?8 ?7 ?6 ?5 ?4 ?3 ?2 ?1 0 1 2 3 4 5 6 7 8 9 10 11 blocking (db) modulated interferer carrier wave interferer 09555-239 figure 22. receiver wideband blocking at 915 mhz, data rate = 300 kbps
adf7023-j rev. 0 | page 22 of 100 ?10 0 10 20 30 40 50 60 70 80 ?60 ?50 ?40 ?30 ?20 ?10 0 10 20 30 40 50 60 blocking (db) blocker frequency offset (mhz) 09555-240 25c, 3.0v figure 23. receiver wideband blocking at 954 mhz, data rate = 50 kbps, frequency deviation = 25 khz, carrier wave interferer, p wanted = p sens + 3 db ?10 70 60 50 40 30 20 10 0 ?1.0 ?0.8 ?0.6 ?0.4 ?0.2 0 0.2 0.4 0.6 0.8 1.0 blocking (db) blocker frequency offset (mhz) 09555-242 25c, 3.0v figure 24. receiver close-in blocking at 954 mhz, data rate = 50 kbps, if filter bandwidth = 100 khz, image calibrated, cw interferer, p wanted = p sens + 3 db ?20 ?10 60 50 40 30 20 10 0 ?1.0 ?0.8 ?0.6 ?0.4 ?0.2 0 0.2 0.4 0.6 0.8 1.0 blocking (db) blocker frequency offset (mhz) 09555-243 25c, 3.0v figure 25. receiver close-in blocking at 954 mhz, data rate = 100 kbps, if filter bandwidth = 100 khz, image calibrated, cw interferer, p wanted = p sens + 3 db ?2.0 ?1.6 ?1.2 0 0.4 0.8 1.2 1.6 2.0 ?20 ?15 ?10 ?5 0 5 10 15 20 25 30 35 40 45 50 55 60 blocking (db) interferer offset from receiver lo frequency (mhz) cw interferer modulated interferer ?0.8 ?0.4 09555-244 figure 26. receiver close-in blocking at 915 mhz, data rate = 150 kbps, if filter bandwidth = 150 khz, image calibrated ?2.0 ?1.6 ?1.2 0 0.4 0.8 1.2 1.6 2.0 ?20 ?15 ?10 ?5 0 5 10 15 20 25 30 35 40 45 50 55 60 blocking (db) interferer offset from receiver lo frequency (mhz) cw interferer modulated interferer ?0.8 ?0.4 09555-245 figure 27. receiver close-in blocking at 915 mhz, data rate = 200 kbps, if filter bandwidth = 200 khz, image calibrated ?2.0 ?1.6 ?1.2 0 0.4 0.8 1.2 1.6 2.0 ?20 ?15 ?10 ?5 0 5 10 15 20 25 30 35 40 45 50 55 60 blocking (db) interferer offset from receiver lo frequency (mhz) cw interferer modulated interferer ?0.8 ?0.4 09555-246 figure 28. receiver close-in blocking at 915 mhz, data rate = 300 kbps, if filter bandwidth = 300 khz, image calibrated
adf7023-j rev. 0 | page 23 of 100 ?90 ?80 ?70 ?60 ?50 ?40 ?30 ?20 ?10 0 ?1.0 ?0.8 ?0.6 ?0.4 ?0.2 0 0.2 0.4 0.6 0.8 1.0 attenuation (db) interferer offset from receiver lo frequency (mhz) calibrated uncalibrated 09555-247 figure 29. image attenuation with calibrated and uncalibrated images, 915 mhz, if filter bandwidth = 100 khz, v dd = 3.0 v, temperature = 25c ?90 ?80 ?70 ?60 ?50 ?40 ?30 ?20 ?10 0 ?1.0 ?0.8 ?0.6 ?0.4 ?0.2 0 0.2 0.4 0.6 0.8 1.0 attenuation (db) offset from lo frequency (mhz) 100khz bw 150khz bw 200khz bw 300khz bw 09555-249 figure 30. if filter profile with calib rated image vs. if fi lter bandwidth, 921 mhz, v dd = 3.0 v, temperature = 25c ?104 ?103 ?102 ?101 ?100 ?99 ? 98 1.8 3.0 3.6 sensitivity (dbm) v dd (v) 915mhz, ?40c 915mhz, +25c 915mhz, +85c 09555-250 figure 31. receiver sensitivity (bit error rate at 1e ? 3) vs. v dd , temperature, and rf frequency, data rate = 300 kbps, gfsk, frequency deviation = 75 khz, if bandwidth = 300 khz ?120 ?115 ?110 ?105 ?100 ? 95 0 50 100 150 200 250 300 sensitivity (dbm) data rate (kbps) bit error rate (1e-3) packet error rate (1%) 09555-251 figure 32. bit error rate sensitivity (at ber = 1e ? 3) and packet error rate sensitivity (at per = 1%) vs. data rate, gfsk, v dd = 3.0 v, temperature = 25c 0 10 20 30 40 50 60 70 80 90 100 packet error rate (%) applied receiver power (dbm) 1kbps 10kbps 38.4kbps 50kbps 100kbps 200kbps 300kbps ?120 ?110 ?100 ?90 ?80 ?70 ?60 ?50 0?10 ?40 ?30 ?20 09555-252 figure 33. packet error rate vs. rf input power and data rate, fsk/gfsk, 928 mhz, preamble length = 64 bits, v dd = 3.0 v, temperature = 25c ?100.0 ?99.5 ?99.0 ?98.5 ?98.0 ?97.5 ?97.0 ?96.5 ? 96.0 1.8 3.6 sensitivity (dbm) v dd (v) ?40c +25c +85c 09555-254 figure 34. receiver sensitivity (packet error rate at 1%) vs. v dd , temperature, and rf frequency, data rate = 300 kbps, gfsk, frequency deviation = 75 khz, if bandwidth = 300 khz
adf7023-j rev. 0 | page 24 of 100 09555-339 10 0 1 2 3 4 5 6 7 8 9 ?107 ?106 ?105 ?104 ?103 ?102 ?101 ?100 ?99 packet error rate (%) rx input power (dbm) coded, pml = 0x0a, sync. tol. = 0 uncoded, pml = 0x0a, sync. tol. = 0 coded, pml = 0x0a, sync. tol. = 1 coded, pml = 0x07, sync. tol. = 2 2.1db 3.5db 4.1db figure 35. receiver per using reed solomon (rs) coding; rf frequency = 928 mhz, gfsk, data rate = 100 kbps, frequency deviation = 50 khz, packet length = 28 bytes (uncoded); reed solomon configuration: n = 38, k = 28, t = 5, pml = preamble match level register 0 ?110 ?100 ?90 ?80 ?70 ?60 ?50 ?40 ?30 ?20 ?10 ?150 150 140 130 120 110 100 90 80 70 60 50 40 30 20 10 0 ?10 ?20 ?30 ?40 ?50 ?60 ?70 ?80 ?90 ?100 ?110 ?120 ?130 ?140 sensitivity (dbm) rf frequency error (khz) 100kbps 150kbps 200kbps 300kbps 09555-259 figure 36. afc on: receiver sensitivity (at per = 1%) vs. rf frequency error, gfsk, 915 mhz, afc enabled (ki = 7, kp = 3), afc mode = lock after preamble, if bandwidth = 100 khz (at 100 kbps), 150 khz (at 150 kbps), 200 khz (at 200 kbps), and 300 khz (at 300 kbps), preamble length = 64 bits 2.00 ?2.00 ?1.75 ?1.50 ?1.25 ?1.00 ?0.75 ?0.50 ?0.25 0 0.25 0.50 0.75 1.00 1.25 1.50 1.75 data rate error (%) ?40 ?30 ?20 ?10 0 10 20 30 ?35 ?25 ?15 ?5 5 15 25 35 40 rf frequency error (khz) >1% <1% 09555-260 figure 37. afc off: packet error rate vs. rf frequency error and data rate error, afc off, data rate = 300 kbps, frequency deviation = 75 khz, gfsk, agc_lock_mode = lock after preamble 2.00 ?2.00 ?1.75 ?1.50 ?1.25 ?1.00 ?0.75 ?0.50 ?0.25 0 0.25 0.50 0.75 1.00 1.25 1.50 1.75 data rate error (%) ?140?120?100 ?80 ?60 ?40 ?20 0 20 40 60 80 100 120 140 rf frequency error (khz) >1% <1 % 09555-261 figure 38. afc on: packet error rate vs. rf frequency error and data rate error, afc on, data rate = 300 kbps, frequency deviation = 75 khz, gfsk, agc_lock_mode = lock after preamble ? 20 ?120 ?110 ?100 ?90 ?80 ?70 ?60 ?50 ?40 ?30 10 ?10 ?8 ?6 ?4 ?2 0 2 4 6 8 rssi (dbm) rssi error (db) ?120 ?110 ?100 ?90 ?80 ?70 ?60 ?50 ?40 ?30 ?20 input power (dbm) ideal rssi mean rssi mean rssi error max positive rssi error max negative rssi error 09555-262 figure 39. rssi (via cmd_get_rssi) vs. rf input power, 950 mhz, gfsk, data rate = 38.4 kbps, frequency deviation = 20 khz, if bandwidth = 100 khz, 100 rssi measurements at each input power level ? 20 ?120 ?110 ?100 ?90 ?80 ?70 ?60 ?50 ?40 ?30 10 ?10 ?8 ?6 ?4 ?2 0 2 4 6 8 rssi (dbm) rssi error (db) ?120 ?110 ?100 ?90 ?80 ?70 ?60 ?50 ?40 ?30 ?20 input power (dbm) ideal rssi mean rssi mean rssi error max positive rssi error max negative rssi error 09555-263 figure 40. rssi (via automatic end of packet rssi measurement) vs. rf input power, 950 mhz, gfsk, data rate = 300 kbps, frequency deviation = 75 khz, if bandwidth = 300 khz, agc_clock_di vide = 15, 100 rssi measurements at each input power level
adf7023-j rev. 0 | page 25 of 100 6 ?6 ?4 ?2 0 2 4 rssi error (db) ?120 ?110 ?100 ?90 ?80 ?70 ?60 ?50 ?40 ?30 ?20 input power (dbm) 300kbps 200kbps 150kbps 100kbps 50kbps 38.4kbps 9.6kbps 09555-264 ?1 1 receiver symbol level 0123456789 sample number 09555-269 figure 44. receiver eye diagram measured using the test dac, rf frequency = 915 mhz, rf input power = ?80 dbm, data rate = 100 kbps, frequency deviation = 50 khz figure 41. mean rssi error (via automatic end of packet rssi measurement) vs. rf input power vs. data rate; rf frequency = 950 mhz, gfsk, 100 rssi measurements at each input power level ? 90 ?91 ?92 ?93 ?94 ?95 ?96 ?97 ?98 ?99 ?100 ?101 ?102 ?103 ?104 ?105 ?106 ?107 ?108 ?109 ?110 220 210 200 190 180 170 160 150 140 130 120 110 100 90 80 70 60 50 40 30 20 sensitivity point (dbm) discriminator bandwidth (khz) 0 0.4 0.8 1.2 1.6 2.0 2.4 2.8 3.2 3.6 4.0 modulation index 09555-349 ifbw = 100khz ifbw = 200khz disc bw (khz) ? 20 ?120 ?110 ?100 ?90 ?80 ?70 ?60 ?50 ?40 ?30 10 ?10 ?8 ?6 ?4 ?2 0 2 4 6 8 rssi (dbm) rssi error (db) ?120 ?110 ?100 ?90 ?80 ?70 ?60 ?50 ?40 ?30 ?20 input power (dbm) ideal rssi mean rssi mean rssi (with polynomial correction) mean rssi error mean rssi error (with polynomial correction) 09555-265 figure 45. rx sensitivity vs. modulation index, data rate = 50 kbps, mod = gfsk, f dev = (mi 2 5 khz), data = prbs9, ber = 1e ? 3, bits = 1e + 6, v bat = 3.0 v, temperature = 25c figure 42. rssi with and without cosine polynomial correction (via automatic end of packet rssi measur ement), 100 rssi measurements at each input power level ? 90 ?91 ?92 ?93 ?94 ?95 ?96 ?97 ?98 ?99 ?100 ?101 ?102 ?103 ?104 ?105 ?106 ?107 ?108 ?109 ?110 220 230 240 210 200 190 180 170 160 150 140 130 120 110 100 90 80 70 60 50 40 sensitivity point (dbm) discriminator bandwidth (khz) 0 0.2 0.4 0.6 0.8 1.0 1.2 1.4 1.6 1.8 2.0 modulation index 09555-350 ifbw = 100khz ifbw = 200khz disc bw (khz) 90 ?40 ?30 ?20 ?10 0 10 20 30 40 50 60 70 80 temperature calculated from sensor (c) ?40 ?30 ?20 ?10 0 10 20 30 40 50 60 8070 90 temperature (c) 09555-347 error + 3 (c) mean (c) error ? 3 (c) figure 46. rx sensitivity vs. modulation index, data rate = 100 kbps, mod = gfsk (0.5), f dev = (mi 50 khz), data = prbs9, ber = 1e ? 3, bits = 2e + 5, v bat = 3.0 v, temperature = 25c figure 43. temperature sensor readba ck vs. die temperature, readback value converted to c via formula in the temperature sensor section
adf7023-j rev. 0 | page 26 of 100 terminology adc analog-to-digital converter agc automatic gain control afc automatic frequency control battmon battery monitor bbram battery backup random access memory cbc cipher block chaining crc cyclic redundancy check dr data rate ecb electronic code book ecc error checking code 2fsk two-level frequency shift keying gfsk two-level gaussian frequency shift keying gmsk gaussian minimum shift keying, gfsk with modulation index = 0.5 lo local oscillator mac media access control mcr modem configuration random access memory mer modulation error ratio msk minimum shift keying, 2fsk with modulation index = 0.5 nop no operation pa power amplifier pfd phase frequency detector phy physical layer rco rc oscillator risc reduced instruction set computer rssi receive signal strength indicator rx receive sar successive approximation register swm smart wake mode tx transmit vco voltage controlled oscillator wuc wa k e - up c o nt r o l l e r xosc crystal oscillator
adf7023-j rev. 0 | page 27 of 100 radio control the adf7023-j has five radio states designated phy_sleep, phy_off, phy_on, phy_tx, and phy_rx. the host processor can transition the adf7023-j between states by issuing single byte commands over the spi interface. the various commands and states are illustrated in figure 47 . the communications processor handles the sequencing of various radio circuits and critical timing functions, thereby simplifying radio operation and easing the burden on the host processor. radio states phy_sleep in this state, the device is in a low power sleep mode. to enter the state, issue the cmd_phy_sleep command, either from the phy_off or phy_on state. to wake the radio from the state, set the cs pin low or use the wake-up controller (32.768 khz rc or 32.768 khz crystal) to wake the radio from this state. the wake-up timer should be set up before entering the phy_sleep state. if retention of bbram contents is not required, deep sleep mode 2 can be used to further reduce the phy_sleep state current consumption. deep sleep mode 2 is entered by issuing the cmd_hw_reset command. the options for the phy_sleep state are detailed in . table 10 phy_off in the phy_off state, the 26 mhz crystal, the digital regulator, and the synthesizer regulator are powered up. all memories are fully accessible. the bbram registers must be valid before exiting this state. phy_on in the phy_on state, along with the crystal, the digital regulator, the synthesizer regulator, the vco, and the rf regulators are powered up. a baseband filter calibration is performed when this state is entered from the phy_off state if the bb_cal bit in the mode_control register (address 0x11a) is set. the device is ready to operate, and the phy_tx and phy_rx states can be entered. phy_tx in the phy_tx state, the synthesizer is enabled and calibrated. the power amplifier is enabled, and the device transmits at the channel frequency defined by the channel_freq[23:0] setting (address 0x109 to address 0x10b). the state is entered by issuing the cmd_phy_tx command. the device automatically transmits the transmit packet stored in the packet ram. after transmission of the packet, the pa is disabled, and the device automatically returns to the phy_on state and can, optionally, generate an interrupt. in sport mode, the device transmits the data present on the gp2 pin as described in the sport mode section. the host processor must issue the cmd_phy_on command to exit the phy_tx state when in sport mode. phy_rx in the phy_rx state, the synthesizer is enabled and calibrated. the adc, rssi, if filter, mixer, and lna are enabled. the radio is in receive mode on the channel frequency defined by the channel_freq[23:0] setting (address 0x109 to address 0x10b). after reception of a valid packet, the device returns to the phy_on state and can, optionally, generate an interrupt. in sport mode, the device remains in the phy_rx state until the cmd_phy_on command is issued. current consumption the typical current consumption in each state is detailed in table 10 . table 10. current consumption in adf7023-j radio states state current (typical) conditions phy_sleep (deep sleep mode 2) 0.18 a wake-up timer off, bbram contents not retained, entered by issuing cmd_hw_reset phy_sleep (deep sleep mode 1) 0.33 a wake-up timer off, bbram contents retained phy_sleep (rco mode ) 0.75 a wake-up timer on using a 32 khz rc oscillator, bbram contents retained phy_sleep (xto mode ) 1.28 a wake-up timer on usin g a 32 khz xtal oscillator, bbram contents retained phy_off 1.0 ma phy_on 1.0 ma phy_tx 24.1 ma 10 dbm, single-ended pa, 950 mhz phy_rx 12.8 ma
adf7023-j rev. 0 | page 28 of 100 configure program ram config aes ir calibration reed-solomon if filter cal configure measure rssi rx_to_tx_auto_turnaround 1 tx_to_rx_auto_turnaround 1 cmd_phy_tx cm d_ p hy _ t x c m d _ p h y _ r x cm d _ p hy _ s l e e p cm d_ p hy _ o n c m d _ p h y _ o n c m d _ p h y _ o n c m d _ p hy _ o f f cmd_phy_rx cold start (battery applied) cmd_config_dev cmd_ram_load_init cmd_ram_load_done c m d_ ae s cmd_ir_cal cmd_aes 4 cs low wuc timeout cmd_phy_sleep cmd_hw_reset (from any state) phy_on phy_tx phy_rx cmd_phy_rx cmd_phy_tx tx_eof 3 rx_eof 3 phy_off phy_sleep cmd_rs 5 cmd_config_dev cmd_bb_cal cmd_get_rssi program ram 2 1 transmit and receive automatic turnaround must be enabled by bits rx_to_tx_auto_turnaround and tx_to_rx_auto_turnaround (0x11a: mode_control). 2 aes encryption/decryption, image rejection calibration, and reed solomon coding are available only if the necessary firmware module has been downloaded to the program ram. 3 the end of frame (eof) automatic transitions are disabled in sport mode. 4 cmd_aes refers to the three available aes commands: cmd_aes_encrypt, cmd_aes_decrypt, and cmd_aes_decrypt_init. 5 cmd_rs refers to the three available reed solomon commands: cmd_rs_encode_init, cmd_rs_encode, and cmd_rs_decode. key transition initiated by host processor automatic transition by communications processor communications processor function downloadable firmware module stored on program ram radio state 4 09555-121 figure 47. radio state diagram
adf7023-j rev. 0 | page 29 of 100 initialization initialization after application of power when power is applied to the adf7023-j (through the vddbat1/vddbat2 pins), it registers a power-on reset (por) event and transitions to the phy_off state. the bbram memory is unknown, the packet ram memory is cleared to 0x00, and the mcr memory is reset to its default values. the host processor should use the following procedure to complete the initialization sequence: 1. bring the cs pin of the spi low and wait until the miso output goes high. 2. issue the cmd_sync command. 3. wait for the cmd_ready bit in the status word to go high. 4. configure the part by writing to all 64 of the bbram registers. 5. issue the cmd_config_dev command so that the radio settings are updated using the bbram values. the adf7023-j is now configured in the phy_off state. initialization after issuing the cmd_hw_reset command th e cmd_hw_reset command performs a full power-down of all hardware, and the device enters the phy_sleep state. to complete the hardware reset, the host processor should complete the following procedure: 1. wa it for 1 ms . 2. bring the cs pin of the spi low and wait until the miso output goes high. the adf7023-j registers a por and enters the phy_off state. 3. issue the cmd_sync command. 4. wait for the cmd_ready bit in the status word to go high. 5. configure the part by writing to all 64 of the bbram registers. 6. issue the cmd_config_dev command so that the radio settings are updated using the bbram values. the adf7023-j is now configured in the phy_off state. initialization on transitioning from phy_sleep (after cs is brought low) the host processor can bring cs low at any time to wake the adf7023-j from the phy_sleep state. this event is not registered as a por event because the bbram contents are valid. the following is the procedure that the host processor is required to follow: 1. bring the cs line of the spi low and wait until the miso output goes high. the adf7023-j enters the phy_off state. 2. issue the cmd_sync command. 3. wait for the cmd_ready bit in the status word to go high. 4. issue the cmd_config_dev command so that the radio settings are updated using the bbram values. the adf7023-j is now configured and ready to transition to the phy_on state. initialization after a wuc timeout th e adf7023-j can autonomously wake from the phy_sleep state using the wake-up controller. if the adf7023-j wakes after a wuc timeout in smart wake mode (swm), it follows the swm routine based on the smart wake mode configuration in bbram (see the low power modes section). if the adf7023-j wakes after a wuc timeout with swm disabled and the firmware timer disabled, it wakes in the phy_off state, and the following is the procedure that the host processor is required to follow: 1. issue the cmd_sync command. 2. wait for the cmd_ready bit in the status word to go high. 3. issue the cmd_config_dev command so that the radio settings are updated using the bbram values. the adf7023-j is now configured in the phy_off state.
adf7023-j rev. 0 | page 30 of 100 commands the commands that are supported by the radio controller are detailed in this section. they initiate transitions between radio states or perform tasks as indicated in figure 47 . the execution times for all radio state transitions are detailed in table 11 and table 12 . cmd_phy_off (0xb0) this command transitions the adf7023-j to the phy_off state. it can be issued in the phy_on state. it powers down the rf and vco regulators. cmd_phy_on (0xb1) this command transitions the adf7023-j to the phy_on state. if the command is issued in the phy_off state, it powers up the rf and vco regulators and performs an if filter calibration if the bb_cal bit is set in the mode_control register (address 0x11a). if the command is issued from the phy_tx state, the host processor performs the following procedure: 1. ramps down the pa. 2. sets the external pa signal low (if enabled). 3. turns off the digital transmit clocks. 4. powers down the synthesizer. 5. sets fw_state = phy_on. if the command is issued from the phy_rx state, the communications processor performs the following procedure: 1. copies the measured rssi to the rssi_readback register. 2. sets the external lna signal low (if enabled). 3. turns off the digital receiver clocks. 4. powers down the synthesizer and the receiver circuitry (adc, rssi, if filter, mixer, and lna). 5. sets fw_state = phy_on. cmd_phy_sleep (0xba) this command transitions the adf7023-j to the very low power phy_sleep state in which the wuc is operational (if enabled), and the bbram contents are retained. it can be issued from the phy_off or phy_on state. cmd_phy_rx (0xb2) th is command can be issued in the phy_on, phy_rx, or phy_tx state. if the command is issued in the phy_on state, the communications processor performs the following procedure: 1. powers up the synthesizer. 2. powers up the receiver circuitry (adc, rssi, if filter, mixer, and lna). 3. sets the rf channel based on the channel_freq[23:0] setting in bbram. 4. sets the synthesizer bandwidth. 5. does a vco calibration. 6. delays for synthesizer settling. 7. enables the digital receiver blocks. 8. sets the external lna enable signal high (if enabled). 9. sets fw_state = phy_rx. if the command is issued in the phy_rx state, the communications processor performs the following procedure: 1. sets the external lna signal low (if enabled). 2. unlocks the afc and agc. 3. turns off the receive blocks. 4. sets the rf channel based on the channel_freq[23:0] setting in bbram. 5. sets the synthesizer bandwidth. 6. does a vco calibration. 7. delays for synthesizer settling. 8. enables the digital receiver blocks. 9. sets the external lna enable signal high (if enabled). 10. sets fw_state = phy_rx. if the command is issued in the phy_tx state, the communications processor performs the following procedure: 1. ramps down the pa. 2. sets the external pa signal low (if enabled). 3. turns off the digital transmit blocks. 4. powers up the receiver circuitry (adc, rssi, if filter, mixer, and lna). 5. sets the rf channel based on the channel_freq[23:0] setting in bbram. 6. sets the synthesizer bandwidth. 7. does a vco calibration. 8. delays for synthesizer settling. 9. enables the digital receiver blocks. 10. sets the external lna enable signal high (if enabled). 11. sets fw_state = phy_rx. cmd_phy_tx (0xb5) th is command can be issued in the phy_on, phy_tx, or phy_rx state. if the command is issued in the phy_on state, the communications processor performs the following procedure: 1. p owers up the synthesizer. 2. sets the rf channel based on the channel_freq[23:0] setting in bbram. 3. sets the synthesizer bandwidth. 4. does a vco calibration. 5. delays for synthesizer settling. 6. enables the digital transmit blocks. 7. sets the external pa enable signal high (if enabled). 8. ramps up the pa. 9. sets fw_state = phy_tx. 10. transmits data.
adf7023-j rev. 0 | page 31 of 100 if the command is issued in the phy_tx state, the communications processor performs the following procedure: 1. r amps down the pa. 2. s ets the external pa enable signal low (if enabled). 3. turns off the digital transmit blocks. 4. sets the rf channel based on the channel_freq[23:0] setting in bbram. 5. sets the synthesizer bandwidth. 6. does a vco calibration. 7. delays for synthesizer settling. 8. enables the digital transmit blocks. 9. sets the external pa enable signal high (if enabled). 10. ramps up the pa. 11. sets fw_state = phy_tx. 12. transmits data. if the command is issued in the phy_rx state, the communications processor performs the following procedure: 1. sets the external lna signal low (if enabled). 2. unlocks the afc and agc. 3. turns off the receive blocks. 4. powers down the receiver circuitry (adc, rssi, if filter, mixer, and lna). 5. sets the rf channel based on the channel_freq[23:0] setting in bbram. 6. sets the synthesizer bandwidth. 7. delays for synthesizer settling. 8. enables the digital transmit blocks. 9. sets the external pa enable signal high (if enabled). 10. ramps up the pa. 11. sets fw_state = phy_tx. 12. transmits data. cmd_config_dev (0xbb) this command interprets the bbram contents and configures each of the radio parameters based on these contents. it can be issued from the phy_off or phy_on state. the only radio parameter that is not configured on this command is the channel_freq[23:0] setting, which instead is configured as part of a cmd_phy_tx or cmd_phy_rx command. the user should write to the entire 64 bytes of the bbram and then issue the cmd_config_dev command, which can be issued in the phy_off or phy_on state. cmd_get_rssi (0xbc) this command turns on the receiver, performs an rssi measure- ment on the current channel, and returns the adf7023-j to the phy_on state. the command can be issued from the phy_on state. the rssi result is saved to the rssi_readback register (address 0x312). this command can be issued from the phy_on state only. cmd_bb_cal (0xbe) this command performs an if filter calibration. it can be issued only in the phy_on state. in many cases, it may not be necessary to use this command because an if filter calibration is automatically performed on the phy_off to phy_on transition if bb_cal = 1 in the mode_control register (address 0x11a). cmd_sync (0xa2) thi s command is used to allow the host processor and communications processor to establish communications. it is required to issue a cmd_sync command during each of the following scenarios: ? a fter application of power ? o n a wuc wake-up ? a fter a cmd_hw_reset ? after a cmd_ram_load_done command has been issued after issuing a cmd_sync command, the host processor should wait until the cmd_ready status bit is high (see the initialization section). this process ensures that the next command issued by the host processor is processed by the communications processor. see the initialization section for further details on using a cmd_sync command. cmd_hw_reset (0xc8) the command performs a full power-down of all hardware, and the device enters the phy_sleep state. this command can be issued in any state and is independent of the state of the communications processor. the procedure for initialization of the device after a cmd_hw_reset command is described in detail in the initialization section. cmd_ram_load_init (0xbf) this command prepares the communications processor for a subsequent download of a software module to program ram. this command should be issued only prior to the program ram being written to by the host processor. cmd_ram_load_done (0xc7) this command is required only after download of a software module to program ram. it indicates to the communications processor that a software module is loaded to program ram. the cmd_ram_load_done command can be issued only in the phy_off state. the command resets the communications processor and the packet ram. this command should be followed by a cmd_sync command. cmd_ir_cal (0xbd) this command performs a fully automatic image rejection calibration on the adf7023-j receiver. this command requires that the ir calibration firmware module has been loaded to the adf7023-j program ram. the firmware module is available from analog devices, inc.. for more information, see the downloadable firmware modules section.
adf7023-j rev. 0 | page 32 of 100 cmd_aes_encrypt (0xd0), cmd_aes_decrypt (0xd2), and cmd_aes_decrypt_init (0xd1) these commands allow aes, 128-bit block encryption and decryption of transmit and receive data using key sizes of 128 bits, 192 bits, or 256 bits. the aes commands require that the aes firmware module has been loaded to the adf7023-j program ram. the aes firmware module is available from analog devices. see the downloadable firmware modules section for details on the aes encryption and decryption module. cmd_rs_encode_init (0xd1), cmd_rs_encode (0xd0), and cmd_rs_decode (0xd2) these commands perform reed-solomon encoding and decoding of transmit and receive data, thereby allowing detection and correction of errors in the received packet. these commands require that the reed-solomon firmware module has been loaded to the adf7023-j program ram. the reed-solomon firmware module is available from analog devices. see the downloadable firmware modules section for details on this module. automatic state transitions on certain events, the communications processor can automatically transition the adf7023-j between states. these automatic transitions are illustrated as dashed lines in figure 47 and are explained in this section. tx_eof th e communications processor automatically transitions the device from the phy_tx state to the phy_on state at the end of a packet transmission. on the transition, the communications processor performs the following actions: 1. ramps down the pa. 2. sets the external pa signal low. 3. disables the digital transmitter blocks. 4. powers down the synthesizer. 5. sets fw_state = phy_on. rx_eof th e communications processor automatically transitions the device from the phy_rx state to the phy_on state at the end of a packet reception. on the transition, the communications processor performs the following actions: 1. c opies the measured rssi to the rssi_readback register (address 0x312). 2. s ets the external lna signal low. 3. d isables the digital receiver blocks. 4. powers down the synthesizer and the receiver circuitry (adc, rssi, if filter, mixer, and lna). 5. sets fw_state = phy_on. rx_to_tx_auto_turnaround i f the rx_to_tx_auto_turnaround bit in the mode_ control register (address 0x11a) is enabled, the device automatically transitions to the phy_tx state at the end of a valid packet reception, on the same rf channel frequency. on the transition, the communications processor performs the following actions: 1. sets the external lna signal low. 2. unlocks the agc and afc (if enabled). 3. disables the digital receiver blocks. 4. powers down the receiver circuitry (adc, rssi, if filter, mixer, and lna). 5. sets rf channel frequency (same as the previous receive channel frequency). 6. sets the synthesizer bandwidth. 7. does vco calibration. 8. delays for synthesizer settling. 9. enables the digital transmitter blocks. 10. sets the external pa signal high (if enabled). 11. ramps up the pa. 12. sets fw_state = phy_tx. 13. transmits data. in sport mode, the rx_to_tx_auto_turnaround transition is disabled. tx_to_rx_auto_turnaround if the tx_to_rx_auto_turnaround bit in the mode_ control register (address 0x11a) is enabled, the device automatically transitions to the phy_rx state at the end of a packet transmission, on the same rf channel frequency. on the transition, the communications processor performs the following actions: 1. ramps down the pa. 2. sets the external pa signal low. 3. disables the digital transmitter blocks. 4. powers up the receiver circuitry (adc, rssi, if filter, mixer, and lna). 5. sets the rf channel (same as the previous transmit channel frequency). 6. sets the synthesizer bandwidth. 7. does vco calibration. 8. delays for synthesizer settling. 9. t urns on agc and afc (if enabled). 10. enables the digital receiver blocks. 11. sets the external lna signal high (if enabled). 12. sets fw_state = phy_rx. in sport mode, the tx_to_rx_auto_turnaround transition is disabled. wuc timeout the adf7023-j can use the wuc to wake from sleep on a timeout of the hardware timer. the device wakes into the phy_off state. see the wuc mode section for further details.
adf7023-j rev. 0 | page 33 of 100 state transition and command timing the execution times for all radio state transitions are detailed in table 11 and table 12 . note that these times are typical and can vary, depending on the bbram configuration. table 11. adf7023-j command execution times and state transi tion times that are not related to phy_tx or phy_rx command/bit command initiated by present state next state transition time (s), typical condition cmd_hw_reset host any phy_sleep 1 cmd_phy_sleep host phy_off phy_sleep 22.3 cmd_phy_sleep host phy_on phy_sleep 24.1 cmd_phy_off host phy_on phy_off 19 cmd_phy_on host phy_off phy_on 248 including if filter calibration cmd_get_rssi host phy_on phy_on 612.5 cmd_config_dev host phy_off phy_off 66.8 cmd_config_dev host phy_on phy_on 66.8 cmd_bb_cal host phy_on phy_on 211 wake-up from phy_sleep, (wuc timeout) automatic phy_sleep phy_off 310 + 252.8 the 310 s is for startup of the 26 mhz crystal (7 pf load capacitance, t a = 25c) wake-up from phy_sleep, ( cs low) host phy_sleep phy_off 310 + 252.8 the 310 s is for startup of the 26 mhz crystal (7 pf load capacitance, t a = 25c) cold start application of power not applicable phy_off 310 + 252.8 the 310 s is for startup of the 26 mhz crystal (7 pf load capacitance, t a = 25c) table 12. adf7023-j state transition times related to phy_tx and phy_rx mode command/bit/ automatic transition present state next state transition time (s) 1 , 2 , typical condition packet cmd_phy_on phy_tx phy_on t eop + 10.8 + t paramp_down + 36 5 + t byte + 38.2 cmd_phy_on issued during search for preamble 41.7 cmd_phy_on issued during preamble qualification 41.2 packet cmd_phy_on phy_rx phy_on t eop + 31.7 cmd_phy_on issued during sync word qualification cmd_phy_on issued during rx data (after a sync word) packet cmd_phy_tx phy_on phy_tx 293 + t paramp_up + 3 5 + t byte + 305.3 + t paramp_up + 3 cmd_phy_tx issued during search for preamble 308.5 + t paramp_up + 3 cmd_phy_tx issued during preamble qualification 308 + t paramp_up + 3 packet cmd_phy_tx phy_rx phy_tx 298.5 + t eop + t paramp_up + 3 cmd_phy_tx issued during sync word qualification cmd_phy_tx issued during rx data (after a sync word) packet cmd_phy_tx phy_tx phy_tx t eop + 10.8 + t paramp_down + 297 + t paramp_up + 3 cmd_phy_tx issued during packet trans- mission packet rx_to_tx_auto _turnaround phy_rx phy_tx 287.3 + t paramp_up + 3 packet cmd_phy_rx phy_on phy_rx 300 packet cmd_phy_rx phy_tx phy_rx t eop + 10.8 + t paramp_down + 317 cmd_phy_rx issued during packet trans- mission
adf7023-j rev. 0 | page 34 of 100 mode command/bit/ automatic transition present state next state transition time (s) 1 , 2 , typical condition 5 + t byte + 305.2 cmd_phy_rx issued during search for preamble 308.4 cmd_phy_rx issued during preamble qualification 307.9 cmd_phy_rx issued during sync word qualification packet cmd_phy_rx phy_rx phy_rx t eop + 298.4 cmd_phy_rx issued during rx data (after a sync word) packet tx_to_rx_auto_ turnaround phy_tx phy_rx 10.8 + t paramp_down + 306 packet tx_eof phy_tx phy_on 10.8 + t paramp_down + 36 packet rx_eof phy_rx phy_on 17.2 sport cmd_phy_on phy_tx phy_on 10.8 + t paramp_down + 36 5 + t byte + 38.2 cmd_phy_on issued during search for a preamble 41.7 cmd_phy_on issued during preamble qualification 41.2 cmd_phy_on issued during sync word qualification sport cmd_phy_on phy_rx phy_on 31.7 cmd_phy_on issued during rx data (after a sync word) sport cmd_phy_tx phy_on phy_tx 293 + t paramp_up + 3 5 + t byte + 305.3 + t paramp_up + 3 cmd_phy_tx issued during search for a preamble 308.5 + t paramp_up + 3 cmd_phy_tx issued during preamble qualification 308 + t paramp_up + 3 cmd_phy_tx issued during sync word qualification sport cmd_phy_tx phy_rx phy_tx 298.5 + t paramp_up + 3 cmd_phy_tx issued during rx data (after a sync word) sport cmd_phy_tx phy_tx phy_tx 10.8 + t paramp_down + 297 + t paramp_up + 3 sport rx_to_tx_auto _turnaround phy_rx phy_tx 287.3 + t paramp_up + 3 sport cmd_phy_rx phy_on phy_rx 300 sport cmd_phy_rx phy_tx phy_rx 10.8 + t paramp_down + 317 5 + t byte + 305.2 cmd_phy_rx issued during search for a preamble 308.4 cmd_phy_rx issued during preamble qualification 307.9 cmd_phy_rx issued during sync word qualification sport cmd_phy_rx phy_rx phy_rx 298.4 cmd_phy_rx issued during rx data (after a sync word) sport tx_to_rx_auto_ turnaround phy_tx phy_rx 10.8 + t paramp_down + 306 1 t paramp_up = t paramp_down = 100 ) (9 2 ? data_rate pa_ramp cr pa_level_m , where pa_level_mcr sets the maximum pa outp ut power (pa_le vel_mcr registe r, address 0x307), pa_ramp sets the pa ramp rate (radio _cfg_8 register, a ddress 0x114), and data_rate sets the transmit data rate (radio_cfg_0 register, address 0x10c and radio_cfg_1 register, address 0x10d). 2 t byte = one byte period (s), t eop = time to end of packet (s).
adf7023-j rev. 0 | page 35 of 100 sport mode it is possible to bypass all of the packet management features of the adf7023-j and use the sport interface for transmit and receive data. the sport interface is a high speed synchronous serial interface allowing direct interfacing to processors and dsps. sport mode is enabled using the data_mode setting in the packet_length_control register (address 0x126), as described in table 13 . the sport mode interface is on the gpio pins (gp0, gp1, gp2, gp4, and xosc32kp_gp5_atb1). these gpio pins can be configured using the gpio_configure setting (address 0x3fa), as described in table 14 . sport mode provides a receive interrupt source on gp4. this interrupt source can be configured to provide an interrupt, or strobe signal, on either preamble detection or sync word detection. the type of interrupt is configured using the gpio_configure setting. packet structure in sport mode in sport mode, the host processor has full control over the packet structure. however, the preamble frame is still required to allow sufficient bits for receiver settling (agc, afc, and cdr). in sport mode, sync word detection is not mandatory in the adf7023-j but can be enabled to provide byte level synchronization for the host processor via the sync word detect interrupt or strobe on gp4. the general format of a sport mode packet is shown in figure 48 . preamble sync word payload 09555-12 8 figure 48. general sport mode packet sport mode in transmit figure 49 illustrates the operation of the sport interface in transmit. once in the phy_tx state with sport mode enabled, the data input of the transmitter is fully controlled by the sport interface (pin gp1). the transmit clock appears on the gp2 pin. the transmit data from the host processor should be synchronized with this clock. the fw_state variable in the status word (see the status word section) or the cmd_finished interrupt (see the interrupts in sport mode section) can be used to indicate when the adf7023-j has reached the phy_tx state and, therefore, is ready to begin transmitting data. the adf7023-j keeps transmitting the serial data presented at the gp1 input until the host processor issues a command to exit the phy_tx state. sport mode in receive the sport interface supports the receive operation with a number of modes to suit particular signaling requirements. the receive data appears on the gp0 pin, whereas the receive synchronized clock appears on the gp2 pin. the gp4 pin provides a dedicated sport mode interrupt or strobe signal on either preamble or sync word detection, as described in table 13 and table 14 . once enabled, the interrupt signal and strobe signals remain operational while in the phy_rx state. the strobe signal gives a single high pulse of 1-bit duration every eight bits. the strobe signal is most useful when used with sync word detection because it is synchronized to the sync word and strobes the first bit in every byte. in sport mode, irq_gp3 retains its normal interrupt functionality for interrupt_source_1; however, only interrupt_preamble_detect and interrupt_ sync_detect are available from interrupt_source_0. refer to the interrupt generation section for more details. transmit bit latencies in sport mode the transmit bit latency is the time from the sampling of a bit by the transmit data clock on gp2 to when that bit appears at the rf output. there is no transmit bit latency when using 2fsk/msk modulation. the latency when using gfsk/gmsk modulation is two bits. it is important that the host processor keep the adf7023-j in the phy_tx state for two bit periods after the last data bit is sampled by the data clock to account for this latency when using gmsk/gfsk modulation. table 13. sport mode setup data_mode bits in packet_length_ control register description gpio configuration data_mode = 0 packet mode enabled. packet management is controlled by the communications processor. data_mode = 1 gp0: rx data gp1: tx data gp2: tx/rx clock gp4: interrupt or strobe en abled on preamble detect (depends on gpio_configure) sport mode enabled. the rx data and rx clock are enabled in the phy_rx state (gpio_configure = 0xa0, 0xa3, 0xa6). the rx clock is enabled in the phy_rx state, and rx data is enabled on the preamble detect (gpio_configure = 0xa1, 0xa2, 0xa4, 0xa5, 0xa7, 0xa8). xosc32kp_gp5_atb1: depends on gpio_configure data_mode = 2 gp0: rx data gp1: tx data gp2: tx/rx clock gp4: interrupt or strobe enabled on sync word detect (depends on gpio_configure) sport mode enabled. the rx data and rx clock are enabled in the phy_rx state if gpio_configure = 0xa0, 0xa3, 0xa6. the rx clock is enabled in the phy_rx state, and rx data is enabled on the preamble detect if gpio_configure = 0xa1, 0xa2, 0xa4, 0xa5, 0xa7, 0xa8. xosc32kp_gp5_atb1: depends on gpio_configure
adf7023-j rev. 0 | page 36 of 100 table 14. gpio functionality in sport mode gpio_configure gp0 gp1 gp2 irq_gp3 gp4 xosc32kp_gp5_atb1 0xa0 rx data tx data tx/r x clock not used not used 0xa1 rx data tx data tx/r x clock interrupt not used 0xa2 rx data tx data tx/rx clock strobe not used 0xa3 rx data tx data tx/rx cl ock not used 32.768 khz xtal input 0xa4 rx data tx data tx/rx clock interrupt 32.768 khz xtal input 0xa5 rx data tx data tx/rx clock strobe 32.768 khz xtal input 0xa6 rx data tx data tx/rx clock not used ext_uc_clk output 0xa7 rx data tx data tx/rx clock interrupt normal interrupt generation from interrupt_source_1. reduced set from interrupt_source_0. refer to interrupts in sport mode. strobe ext_uc_clk output ext_uc_clk output 0xa8 rx data tx data tx/rx clock preamble sync word payload pa ramp 55.4s pa ramp 300s phy_on phy_tx cmd_phy_on cmd_phy_tx packet irq_gp3 (cmd_finished interrupt) gp2 (tx clk) gp1 (tx data) gp2 (tx clk) gp1 (tx data) 09555-129 figure 49. sport mode transmit preamble sync word payload 55.4s 309s phy_on phy_rx cmd_phy_on c md_phy_rx packet gp4 gp2 (rx clk) gp0 (rx data) gp2 (rx clk) gp0 (rx data) 09555-130 figure 50. sport mode receive, data_mode = 1, 2 and gpio_configure = 0xa0, 0xa3, or 0xa6
adf7023-j rev. 0 | page 37 of 100 preamble sync word preamble detected payload 55.4s 309s phy_on phy_rx cmd_phy_on cmd_phy_rx packet gp4 (gpio_configure = 0xa1) gp4 (gpio_configure = 0xa2) gp2 (rx clk) gp0 (rx data) gp4 (gpio_configure = 0xa1) gp4 (gpio_configure = 0xa2) gp2 (rx clk) gp0 (rx data) 8/(data rate) 09555-131 figure 51. sport mode receive, data_mode = 1, gpio_configure = 0xa1, 0xa2, 0xa4, 0xa5, 0xa7, 0xa8 preamble sync word payload 55.4s 309s phy_on phy_rx cmd_phy_on cmd_phy_rx packet gp4 (gpio_configure = 0xa1) gp4 (gpio_configure = 0xa2) gp2 (rx clk) gp0 (rx data) gp4 (gpio_configure = 0xa1) gp4 (gpio_configure = 0xa2) gp2 (rx clk) gp0 (rx data) 09555-132 figure 52. sport mode receive, data_mode = 2, gpio_configure = 0xa1, 0xa2, 0xa4, 0xa5, 0xa7, 0xa8
adf7023-j rev. 0 | page 38 of 100 packet mode the on-chip communications processor can be configured for use with a wide variety of packet-based radio protocols using 2fsk/gfsk/msk/gmsk modulation. the general packet format, when using the packet management features of the communications processor, is illustrated in table 16 . to use the packet management features, the data_mode setting in the packet_length_control register (address 0x126) should be set to packet mode; 240 bytes of dedicated packet ram are available to store, transmit, and receive packets. in transmit mode, preamble, sync word, and crc can be added by the communications processor to the data stored in the packet ram for transmission. in addition, all packet data after the sync word can be optionally whitened, manchester encoded, or 8b/10b encoded on transmission and decoded on reception. in receive mode, the communications processor can be used to qualify received packets based on the preamble detection, sync word detection, crc detection, or address match and generate an interrupt on the irq_gp3 pin. on reception of a valid packet, the received payload data is loaded to packet ram memory. more information on interrupts is contained in the interrupt generation section. preamble the preamble is a mandatory part of the packet that is automatically added by the communications processor when transmitting a packet and removed after receiving a packet. the preamble is a 0x55 sequence, with a programmable length between 1 byte and 256 bytes, that is set in the preamble_len register (address 0x11d). it is necessary to have preamble at the beginning of the packet to allow time for the receiver agc, afc, and clock and data recovery circuitry to settle before the start of the sync word. the required preamble length depends on the radio configuration. see the radio blocks section for more details. in receive mode, the adf7023-j can use a preamble qualification circuit to detect preamble and interrupt the host processor. the preamble qualification circuit tracks the received frame as a sliding window. the window is three bytes in length, and the preamble pattern is fixed at 0x55. the preamble bits are examined in 01pairs. if either bit or both bits are in error, the pair is deemed erroneous. the possible erroneous pairs are 00, 11, and 10. the number of erroneous pairs tolerated in the preamble can be set using the preamble_match re gister value (address 0x11b) according to table 15 . table 15. preamble detection tolerance (preamble_match, address 0x11b) value description 0x0c no errors allowed. 0x0b one erroneous bit-pair allowed in 12 bit-pairs. 0x0a two erroneous bit-pairs allowed in 12 bit-pairs. 0x09 three erroneous bit-pairs allowed in 12 bit-pairs. 0x08 four erroneous bit-pairs allowed in 12 bit-pairs. 0x00 preamble detection disabled. table 16. adf7023-j packet structure description packet structure 1 payload packet format options preamble sync length address payload data crc postamble field length 1 byte to 256 bytes 1 bit to 24 bits 1 byte 1 byte to 9 bytes 0 bytes to 240 bytes 2 bytes 2 bytes optional field in packet structure x x yes yes yes yes x comms processor adds in tx, remo ves in rx yes yes x x x yes yes host writes these fields to packet ram x x yes yes yes x x whitening/dewhitening (optional) x x yes yes yes yes x manchester encoding/decoding (optional) x x yes yes yes yes x 8b/10b encoding/decoding (optional) x x yes yes yes yes x configurable parameter yes yes yes yes yes yes x receive interrupt on valid field detection yes yes x yes x yes x programmable field error tolerance yes yes x x x x x programmable field offset (see figure 55 ) x x x yes x x x 1 yes indicates that the packet format option is supported, and x indicates that the packet format option is not supported.
adf7023-j rev. 0 | page 39 of 100 if preamble_match is set to 0x0c, the adf7023-j must receive 12 consecutive 01 pairs (three bytes) to confirm that valid preamble has been detected. the user can select the option to automatically lock the afc and/or agc once the qualified preamble is detected. the afc lock on preamble detection can be enabled by setting afc_lock_mode = 3 in the radio_cfg_10 register (address 0x116). the agc lock on preamble detection can be enabled by setting agc_lock_ mode = 3 in the radio_cfg_7 register (address 0x113). after the preamble is detected and the end of preamble has been reached, the communications processor searches for the sync word. the search for the sync word lasts for a duration equal to the sum of the number of programmed sync word bits, plus the preamble matching tolerance (in bits) plus 16 bits. if the sync word routine is detected during this duration, the communications processor loads the received payload to packet ram and computes the crc (if enabled). if the sync word routine is not detected during this duration, the communications processor continues searching for the preamble. preamble detection can be disabled by setting the preamble_ match register to 0x00. to enable an interrupt upon preamble detection, the user must se t interrupt_prea mble_detect = 1 in the interrupt_mask_0 register (address 0x100). sync word sync word is the synchronization word used by the receiver for byte level synchronization while also providing an optional interrupt on detection. it is automatically added to the packet by the communications processor in transmit mode and removed during reception of a packet. the value of the sync word is set in the sync_byte_0, sync_byte_1, and sync_byte_2 registers (address 0x121, address 0x122, and address 0x123, respectively) . the sync word is transmitted most significant bit first starting with sync_byte_0 . the sync word matching length at the receiver is set using sync_word_length in the sync_control register (address 0x120) and can be one bit to 24 bits long; the transmitted sync word is a multiple of eight bits. therefore, for nonbyte length sync words, the transmitted sync pattern should be appended with the preamble pattern as described in figure 53 and table 18 . in receive mode, the adf7023-j can provide an interrupt on reception of the sync word sequence programmed in the sync_byte_0, sync_byte_1, and sync_byte_2 registers. this feature can be used to alert the host processor that a qualified sync word has been received. an error tolerance parameter can also be programmed that accepts a valid match when up to three bits of the sync word sequence are incorrect. the error tolerance value is set using the sync_error_tol setting in the sync_control register (address 0x120), as described in table 17 . table 17. sync word detection tolerance (sync_error_tol, bits[7:6] of address 0x120) value description 00 no bit errors allowed. 01 one bit error allowed. 10 two bit errors allowed. 11 three bit errors allowed. sync_byte_2 sync_byte_1 sync_byte_0 2 4 bits sync_word_length > 16 bits append unused bits with preamble (0101..) first bit sent msb lsb sync_byte_2 sync_byte_1 16 bits sync_word_length > 8 bits append unused bits with preamble (0101..) msb lsb sync_byte_2 sync_word_length 8 bits append unused bits with preamble (0101..) msb lsb 09555-068 figure 53. transmit sy nc word configuration
adf7023-j rev. 0 | page 40 of 100 table 18. sync word programming examples required sync word (binary, first bit being first in time) ? sync_word_ length bits in sync_control register (0x120) sync_ byte_0 1 sync_ byte_1 1 sync_ byte_2 transmitted sync word (binary, first bit being first in time) receiver sync word match length (bits) 000100100011010001010110 24 0x12 0x34 0x56 0001_0010_0011_0100_0101_0110 24 111010011100101000100 21 0x5d 0x39 0x44 0101_1101_0011_1001_0100_0100 21 0001001000110100 16 0xxx 0x12 0x34 0001_0010_0011_0100 16 011100001110 12 0xxx 0x57 0x0e 0101_0111_0000_1110 12 00010010 8 0xxx 0xxx 0x12 0001_0010 8 011100 6 0xxx 0xxx 0x5c 0101_1100 6 1 x = dont care. choice of sync word the sync word should be chosen to have low correlation with the preamble and have good autocorrelation properties. when the afc is set to lock on detection of sync word (afc_lock_mode = 3 and preamble_match = 0), the sync word should be chosen to be dc free, and it should have a run length limit not greater than four bits. payload the host processor writes the transmit data payload to the packet ram. the location of the transmit data in the packet ram is defined by the tx_base_adr value register (address 0x124). the tx_base_adr value is the location of the first byte of the transmit payload data in the packet ram. on reception of a valid sync word, the communications processor automatically loads the receive payload to the packet ram. the rx_base_adr register value (address 0x125) sets the location in the packet ram of the first byte of the received payload. for more details on packet ram memory, see the adf7023-j memory map section. byte orientation the over-the-air arrangement of each transmitted packet ram byte can be set to msb first or lsb first using the data_byte setting in the packet_length_control register (address 0x126). the same orientation setting should be used on the transmit and receive sides of the rf link. packet length modes the adf7023-j can be used in both fixed and variable length packet systems. fixed or variable length packet mode is set using the packet_len variable setting in the packet_ length_control register (address 0x126). for a fixed packet length system, the length of the transmit and received payload is set by the packet_length_max register (address 0x127). the payload length is defined as the number of bytes from the end of the sync word to the start of the crc. in variable packet length mode, the communications processor extracts the length field from the received payload data. in transmit mode, the length field must be the first byte in the transmit payload. the communications processor calculates the actual received payload length as rxpayload length = length + length_offset ? 4 where: length is the length field (the first byte in the received payload). length_offset is a programmable offset (set in the packet_length_control register (address 0x126). the length_offset value allows compatibility with systems where the length field in the proprietary packet may also include the length of the crc and/or the sync word. the adf7023-j defines the payload length as the number of bytes from the end of the sync word to the start of the crc. in variable packet length mode, the packet_length_max value defines the maximum packet length that can be received, as described in figure 54 . fixed tx payload length = packet_length_max rx payload length = packet_length_max tx payload length = length rx payload length = length + length_offset ? 4 preamble sync word length variable payload crc preamble sync word payload crc 09555-125 figure 54. payload length in fixed and variable length packet modes addressing the adf7023-j provides a very flexible address matching scheme, allowing matching of a single address, multiple addresses, and broadcast addresses. the address information can be included at any section of the transmit payload. the location of the starting byte of the address data in the received payload is set in the address_match_offset register (address 0x129), as illustrated in figure 55 . the number of bytes in the first address field is set in the address_length register (address 0x12a). these settings allow the communications processor to extract the address information from the received packet.
adf7023-j rev. 0 | page 41 of 100 the address data is then compared against a list of known addresses that are stored in bbram (address 0x12b to address 0x13d). each stored address byte has an associated mask byte, thereby allowing matching of partial sections of the address bytes, which is useful for checking broadcast addresses or a family of addresses that have a unique identifier in the address sequence. the format and placement of the address information in the payload data should match the address check settings at the receiver to ensure exact address detection and qualification. table 19 shows the register locations in the bbram that are used for setup of the address checking. when register 0x12a (number of bytes in the first address field) is set to 0x00, address checking is disabled. address_match_offset preamble sync word address data payload crc 09555-126 figure 55. address match offset table 19. address check register setup address (bbram) description 1 0x129, address_match_ offset position of first address byte in the received packet (first byte after sync word = 0) 0x12a, address_length number of bytes in the first address field (n adr_1 ) 0x12b address 1 match byte 0 0x12c address 1 mask byte 0 0x12d address 1 match byte 1 0x12e address 1 mask byte 1 address 1 match byte n adr_1 ? 1 address 1 mask byte n adr_1 ? 1 0x00 to end or n adr_2 for another address check sequence 1 n adr_1 = the number of bytes in the first address field; n adr_2 = the number of bytes in the second address field. the host processor should set the interrupt_address_ match bit in the interrupt_source_0 register (address 0x336) if an interrupt is required on the irg_gp3 pin. additional information on interrupts is contained in the interrupt generation section. example address check consider a system with 32-bit address lengths, in which the first byte is located in the 10 th byte of the received payload data. the system also uses broadcast addresses in which the first byte is always 0xaa. to match the exact address, 0xabcdef01 or any broadcast address in the form 0xaaxxxxxx, the adf 7023-j must be configured as shown in table 20 . table 20. example address check configuration bbram address value description 0x129 0x09 location in payload of the first address byte 0x12a 0x04 number of bytes in the first address field, n adr_1 = 4 0x12b 0xab address 1 match byte 0 0x12c 0xff address 1 mask byte 0 0x12d 0xcd address 1 match byte 1 0x12e 0xff address 1 mask byte 1 0x12f 0xef address 1 match byte 2 0x130 0xff address 1 mask byte 2 0x131 0x01 address 1 match byte 3 0x132 0xff address 1 mask byte 3 0x133 0x04 number of bytes in the second address field, n adr_2 = 4 0x134 0xaa address 2 match byte 0 0x135 0xff address 2 mask byte 0 0x136 0x00 address 2 match byte 1 0x137 0x00 address 2 mask byte 1 0x138 0x00 address 2 match byte 2 0x139 0x00 address 2 mask byte 2 0x13a 0x00 address 2 match byte 3 0x13b 0x00 address 2 mask byte 3 0x13c 0x00 end of addresses (indicated by 0x00) 0x13d 0xxx dont care crc an optional crc-16 can be appended to the packet by setting crc_en =1 in the packet _length_control register (address 0x126). in receive mode, this bit enables crc detection on the received packet. a default polynomial is used if prog_crc_en = 0 in the symbol_mode register (address 0x11c). the default crc polynomial is g ( x ) = x 16 + x 12 + x 5 + 1 any other 16-bit polynomial can be used if prog_crc_en = 1, and the polynomial is set in crc_poly_0 and crc_poly_1 (address 0x11e and address 0x11f, respectively). the setup of the crc is described in table 2 1 . table 21.crc setup crc_en bit in the packet_ length control register prog_ crc_en bit in the symbol_ mode register description 0 x 1 crc is disabled in transmit, and crc detection is disabled in receive. 1 0 crc is enabled in transmit, and crc detection is enabled in receive, with the default crc polynomial. 1 1 crc is enabled in transmit, and crc detection is enabled in receive, with the crc polynomial defined by crc_poly_0 and crc_poly_1. 1 x = dont care.
adf7023-j rev. 0 | page 42 of 100 to convert a user-defined polynomial to the 2-byte value, the polynomial should be written in binary format. the x 16 coefficient is assumed equal to 1 and is, therefore, discarded. the remaining 16 bits then make up crc_poly_0 (most significant byte) and crc_poly_1 (least significant byte). two examples of setting common 16-bit crcs are shown in table 22 . postamble the communications processor automatically appends two bytes of postamble to the end of the transmitted packet. each byte of the postamble is 0x55. the first byte is transmitted immediately after the crc. the pa ramp-down begins immediately after the first postamble byte. the second byte is transmitted while the pa is ramping down. table 22. example programming of crc_poly_0 and crc_poly_1 polynomial binary format crc_poly_0 on the receiver, if the received packet is valid, the rssi is automatically measured during the first postamble byte, and the result is stored in the rssi_readback register (address 0x312). the rssi is measured by the communications processor 17 s after the last crc bit. crc_poly_1 x 16 + x 15 + x 2 + 1 (crc-16-ibm) 1_1000_0000_ 0000_0101 0x80 0x05 x 16 + x 13 + x 12 + x 11 x 10 + x 8 + x 6 + x 5 + x 2 + 1 (crc-16-dnp) 1_0011_1101_ 0110_0101 0x3d 0x65 transmit packet timing the pa ramp timing in relation to the transmit packet data is described in figure 56 . after the cmd_phy_tx command is issued, a vco calibration is carried out, followed by a delay for synthesizer settling. the pa ramp follows the synthesizer settling. after the pa is ramped up to the programmed rate, there is 1-byte delay before the start of modulation (preamble). at the beginning of the second byte of postamble, the pa ramps down. the communications processor then transitions to the phy_on state or the phy_rx state (if the tx_to_rx_auto_turnaround is enabled or the cmd_phy_rx command is issued). to enable crc detection on the receiver, with the default crc or user-defined 16-bit crc, crc_en in the packet_length_ control register (address 0x126) should be set to 1. an interrupt can be generated on reception of a crc verified packet (see the interrupt generation section). 142s 55s 300s vco cal synth preamble sync word crc postamble payload phy_tx = 0x14 (phy_tx) = 0x00 (busy) pa ramp pa ramp 1 byte ramp time ramp time ~19s cmd_phy_tx pa output tx data communications processor fw_state 09555-127 figure 56. transmit packet timing
adf7023-j rev. 0 | page 43 of 100 data whitening data whitening can be employed to avoid long runs of 1s or 0s in the transmitted data stream. this ensures sufficient bit transitions in the packet, which aids in receiver clock and data recovery because the encoding breaks up long runs of 1s or 0s in the transmit packet. the data, excluding the preamble and sync word, is automatically whitened before transmission by xoring the data with an 8-bit pseudorandom sequence. at the receiver, the data is xored with the same pseudorandom sequence, thereby reversing the whitening. the linear feedback shift register polynomial used is x 7 + x 1 + 1. data whitening and dewhitening are enabled by setting data_whitening = 1 in the symbol_mode register (address 0x11c). manchester encoding manchester encoding can be used to ensure a dc-free (zero mean) transmission. the encoded over-the-air bit rate (chip rate) is double the rate set by the data_rate variable (address 0x10c and address 0x10d). a binary 0 is mapped to 10, and a binary 1 is mapped to 01. manchester encoding and decoding are applied to the payload data and the crc. manchester encoding and decoding are enabled by setting manchester_enc = 1 in the symbol_mode register (address 0x11c). 8b/10b encoding 8b/10b encoding is a byte-orientated encoding scheme that maps an 8-bit byte to a 10-bit data block. it ensures that the maximum number of consecutive 1s or 0s (that is, run length) in any 10-bit transmitted symbol is five. the advantage of this encoding scheme is that dc balancing is employed without the efficiency loss of manchester encoding. the rate loss for 8b/10b encoding is 0.8, whereas for manchester encoding, it is 0.5. encoding and decoding are applied to the payload data and the crc. the 8b/10b encoding and decoding are enabled by setting eight_ten_enc =1 in the symbol_mode register (address 0x11c).
adf7023-j rev. 0 | page 44 of 100 interrupt generation the adf7023-j uses a highly flexible, powerful interrupt system with support for mac level interrupts and phy level interrupts. to enable an interrupt source, the corresponding mask bit must be set. when an enabled interrupt occurs, the irq_gp3 pin goes high, and the interrupt bit of the status word is set to logic 1. the host processor can use either the irq_gp3 pin or the status word to check for an interrupt. after an interrupt is asserted, the adf7023-j continues operations unaffected, unless it is directed to do otherwise by the host processor. an outline of the interrupt source and mask system is shown in tabl e 23 . mac interrupts can be enabled by writing a logic 1 to the relevant bits of the interrupt_mask_0 register (address 0x100) and phy level interrupts by writing a logic 1 to the relevant bits of the interrupt_mask_1 register (address 0x101). the structure of these memory locations is described in table 23 . in the case of an interrupt condition, the interrupt source can be determined by reading the interrupt_source_0 register (address 0x336) and the interrupt_source_1 register (address 0x337). the bit that corresponds to the relevant interrupt condition is high. the structure of these two registers is shown in table 24 . following an interrupt condition, the host processor should clear the relevant interrupt flag so that further interrupts assert the irq_gp3 pin. this is performed by writing a logic 1 to the bit that is high in either the interrupt_source_0 or the interrupt_source_1 register. if multiple bits in the interrupt source registers are high, they can be cleared individually or altogether by writing logic 1 to them. the irq_gp3 pin goes low when all the interrupt source bits are cleared. as an example, take the case where a battery alarm (in the interrupt_source_1 register) interrupt occurs. the host processor should do the following: 1. read the interrupt source registers. in this example, if none of the interrupt flags in interrupt_source_0 are enabled, only interrupt_source_1 must be read. 2. clear the interrupt by writing 0x80 (or 0xff) to interrupt_source_1. 3. respond to the interrupt condition. table 23. structure of the interrupt mask registers register bit name description interrupt_mask_0, address 0x100 7 interrupt_num_wakeups interrupt when the number of wuc wake-ups (number_of_wakeups[15:0]) has reached the threshold (number_of_wakeups_irq_threshold[15:0]) 1: interrupt enabled; 0: interrupt disabled 6 interrupt_swm_rssi_det interrupt when the measured rssi during smart wake mode has exceeded the rssi threshold value (swm_rssi_thresh, address 0x108) 1: interrupt enabled; 0: interrupt disabled 5 interrupt_aes_done interrupt when an aes encrypti on or decryption command is complete; available only when th e aes firmware module has been loaded to the adf7023-j program ram 1: interrupt enabled; 0: interrupt disabled 4 interrupt_tx_eof interrupt when a packet has finished transmitting 1: interrupt enabled; 0: interrupt disabled 3 interrupt_address_match interrupt when a received packet has a valid address match 1: interrupt enabled; 0: interrupt disabled 2 interrupt_crc_correct interrupt when a received packet has the correct crc 1: interrupt enabled; 0: interrupt disabled 1 interrupt_sync_detect interrupt when a qualified sync word has been detected in the received packet 1: interrupt enabled; 0: interrupt disabled 0 interrupt_preamble_detect interrupt when a qualified preamble has been detected in the received packet 1: interrupt enabled; 0: interrupt disabled
adf7023-j rev. 0 | page 45 of 100 register bit name description interrupt_mask_1, address 0x101 7 battery_alarm interrupt when the battery voltage has dropped below the threshold value (battery_monitor_threshold_voltage, address 0x32d) 1: interrupt enabled; 0: interrupt disabled 6 cmd_ready interrupt when the communications processor is ready to load a new command; mirrors the cmd_ready bit of the status word 1: interrupt enabled; 0: interrupt disabled 5 reserved 4 wuc_timeout interrupt when the wuc has timed out 1: interrupt enabled; 0: interrupt disabled 3 reserved 2 reserved 1 spi_ready interrupt when the spi is ready for access 1: interrupt enabled; 0: interrupt disabled 0 cmd_finished interrupt when the communications processor has finished performing a command 1: interrupt enabled; 0: interrupt disabled table 24. structure of the interrupt source registers register bit name interrupt description interrupt_source_0, address: 0x336 7 interrupt_num_wakeups asserted when the number of wuc wake-ups (number_of_wakeups[15:0]) has reached the threshold (number_of_wakeups_irq_threshold[15:0]) 6 interrupt_swm_rssi_det asserted when the measured rssi during smart wake mode has exceeded the rssi threshold value (swm_rssi_thresh, address 0x108) 5 interrupt_aes_done asserted when an aes encryption or decryption command is complete; available only when th e aes firmware module has been loaded to the adf7023-j program ram 4 interrupt_tx_eof asserted when a packet has finished transmitti ng (packet mode only) 3 interrupt_address_match asserted when a received packet has a valid address match (packet mode only) 2 interrupt_crc_correct asserted when a received packet has the correct crc (packet mode only) 1 interrupt_sync_detect asserted when a qualified sync word has been detected in the received packet 0 interrupt_preamble_detect asserted when a qualified preamble has been detected in the received packet interrupt_source_1, address: 0x337 7 battery_alarm asserted when the battery voltage has dropped below the threshold value (battery_monitor_threshold_voltage, address 0x32d) 6 cmd_ready asserted when the communications processor is ready to load a new command; mirrors the cmd_ready bit of the status word 5 reserved 4 wuc_timeout asserted when the wuc has timed out 3 reserved 2 reserved 1 spi_ready asserted when the spi is ready for access 0 cmd_finished asserted when the communications processor has finished performing a command
adf7023-j rev. 0 | page 46 of 100 interrupts in sport mode in sport mode, the interrupts from interrupt_source_1 are all available. however, only interrupt_preamble_detect and interrupt_sync_detect are available from interrupt_source_0. a second interrupt pin is provided on gp4, which gives a dedicated sport mode interrupt on either preamble or sync word detection. for more details, see the sport mode section. following receipt of the packet in sport mode, re-issue the phy_rx command to re-enable the interrupts for the next packet.
adf7023-j rev. 0 | page 47 of 100 adf7023-j memory map spi cs miso mosi sclk data[7:0] address[10:0] not used reserved 0x100 0x13f 0x300 0x3ff 0x0ff 0x010 0x00f 0x000 address [12:0] program ram 2kb program rom 4kb mcr 256 bytes bbram 64 bytes packet ram 256 bytes instruction/data [7:0] 11-bi t addresses address/ data mux spi/cp memory arbitration comms processo r clock comms processor 8-bit risc engine 09555-070 figure 57. adf7023-j memory map this section describes the various memory locations used by the adf7023-j. the radio control, packet management, and smart wake mode capabilities of the part are realized using an integrated risc processor, which executes instructions stored in the embedded program rom. there is also a local ram, subdivided into three sections, that is used as a data packet buffer, both for transmitted and received data (packet ram), and for storing the radio and packet management configuration (bbram and mcr). the ram addresses of these memory banks are 11 bits long. bbram the battery backup ram contains the main radio and packet management registers used to configure the radio. on application of battery power to the adf7023-j for the first time, the entire bbram should be initialized by the host processor with the appropriate settings. after the bbram is written to, the cmd_config_dev command should be issued to update the radio and communications processor with the current bbram settings. the cmd_config_dev command can be issued in the phy_off state or the phy_on state only. the bbram is used to maintain settings needed at wake-up from sleep mode by the wake-up controller. upon wake-up from sleep, in smart wake mode, the bbram contents are read by the on-chip processor to recover the packet management and radio parameters. modem configuration ram (mcr) the 256-byte modem configuration ram (mcr) contains the various registers used for direct control or observation of the physical layer radio blocks of the adf7023-j. the contents of the mcr are not retained in the phy_sleep state. program rom the program rom consists of 4 kb of nonvolatile memory. it contains the firmware code for radio control, packet management, and smart wake mode. program ram the program ram consists of 2 kb of volatile memory. this memory space is used for software modules, such as aes encryption, ir calibration, and reed-solomon coding, which are available from analog devices. the software modules are downloaded to the program ram memory space over the spi by the host processor. see the downloadable firmware modules section for details on loading a firmware module to program ram.
adf7023-j rev. 0 | page 48 of 100 packet ram the packet ram consists of 256 bytes of memory space. the first 16 bytes of this memory space are allocated for use by the on-chip processor. the remaining 240 bytes of this memory space are allocated for storage of data from valid received packets and packet data to be transmitted. the communications processor stores received payload data at the memory location indicated by the value of the rx_base_adr register (address 0x125), the receive address pointer. the value of the tx_base_adr register (address 0x124), the transmit address pointer, determines the start address of data to be transmitted by the communications processor. this memory can be arbitrarily assigned to store single or multiple transmit or receive packets, with and without overlap. the rx_base_adr value should be chosen to ensure that there is enough allocated packet ram space for the maximum receiver payload length. transmit or receive payload transmit payload receive payload transmit payload receive payload receive payload 2 transmit payload 2 multiple transmit and receive packets 240 byte transmit or receive packet transmit and receive packet 0x010 0x0ff 0x010 0x0ff 0x010 0x0ff tx_base_adr (packet 1) tx_base_adr rx_base_adr tx_base_adr rx_base_adr tx_base_adr (packet 2) rx_base_adr (packet 1) rx_base_adr (packet 2) 09555-071 figure 58. example packet ram configurations using the tx packet and rx packet address pointers
adf7023-j rev. 0 | page 49 of 100 spi interface general characteristics the adf7023-j is equipped with a 4-wire spi interface, using the sclk, miso, mosi, and cs pins. the adf7023-j always acts as a slave to the host processor. shows an example connection diagram between the processor and the adf7023-j. the diagram also shows the direction of the signal flow for each pin. the spi interface is active, and the miso outputs enabled, only while the figure 59 cs input is low. the interface uses a word length of eight bits, which is compatible with the spi hardware of most processors. the data transfer through the spi interface occurs with the most significant bit first. the mosi input is sampled at the rising edge of sclk. as commands or data are shifted in from the mosi input at the sclk rising edge, the status word or data is shifted out at the miso pin synchronous with the sclk clock falling edge. if cs is brought low, the most significant bit of the status word appears on the miso output without the need for a rising clock edge on the sclk input. adf7023-j host processor sclk mosi miso irq_gp3 gpio sclk mosi miso irq cs 09555-026 figure 59. spi interface connections command access the adf7023-j is controlled through commands. command words are single octet instructions that control the state transitions of the communications processor and access to the registers and packet ram. the complete list of valid commands is given in the command reference section. commands that have a cmd prefix are handled by the communications processor. memory access commands have an spi prefix and are handled by an independent controller. thus, spi commands can be issued independent of the state of the communications processor. a command is initiated by bringing cs low and shifting in the command word over the spi, as shown in . all commands are executed after figure 60 cs goes high again or at the next positive edge of the sclk input. the latter condition occurs in the case of a memory access command, in which case the command is executed on the positive sclk clock edge corresponding to the most significant bit of the first parameter word. the cs input must be brought high again after a command has been shifted into the adf7023-j to enable the recognition of successive command words. this is because a single command can be issued only during a cs low period (with the exception of a double nop command). cmd ignore cs mosi miso 09555-027 figure 60. command write (no parameters) status word the status word of the adf7023-j is automatically returned over the miso each time a byte is transferred over the mosi. shifting in double spi_nop commands (see table 27 ) causes the status word to be shifted out as shown in figure 61 . the meaning of the various bit fields is illustrated in table 25 . the fw_state variable can be used to read the current state of the communications processor and is described in table 26 . if it is busy performing an action or state transition, fw_state is busy. the fw_state variable also indicates the current state of the radio. the spi_ready variable is used to indicate when the spi is ready for access. the cmd_ready variable is used to indicate when the communications processor is ready to accept a new command. the status word should be polled and the cmd_ready bit examined before issuing a command to ensure that the communications processor is ready to accept a new command. it is not necessary to check the cmd_ready bit before issuing a spi memory access command. it is possible to queue one command while the communications processor is busy. this is discussed in the command queuing section. the adf7023-j interrupt handler can also be configured to generate an interrupt signal on irq_gp3 when the communications processor is ready to accept a new command (cmd_ready in the interrupt_source_1 register [address 0x337]) or when it has finished processing a command (cmd_finished in the interrupt_source_1 register [address 0x337]). mosi cs miso spi_nop spi_nop ignore status 09555-028 figure 61. reading the status word using a double spi_nop command table 25. status word bit name description [7] spi_ready 0: spi is not ready for access. 1: spi is ready for access. [6] irq_status 0: no pending interrupt condition. 1: pending interrupt condition (mirrors the irq_gp3 pin). [5] cmd_ready 0: the radio controller is not ready to receive a radio controller command. 1: the radio controller is ready to receive a radio controller command. [4:0] fw_state indicates the adf7023-j state (in table 26 ).
adf7023-j rev. 0 | page 50 of 100 table 26. fw_state description value state 0x0f initializing 0x00 busy, performing a state transition 0x11 phy_off 0x12 phy_on 0x13 phy_rx 0x14 phy_tx 0x06 phy_sleep 0x05 performing cmd_get_rssi 0x07 performing cmd_ir_cal 0x08 performing cmd_aes_decrypt_init 0x09 performing cmd_aes_decrypt 0x0a performing cmd_aes_encrypt command queuing the cmd_ready status bit is used to indicate that the command queue used by the communications processor is empty. the queue is one command deep. the fw_state bit is used to indicate the state of the communications processor. the operation of the status word and these bits is illustrated in figure 62 when a cmd_phy_on command is issued in the phy_off state. operation of the status word when a command is being queued is illustrated in figure 63 when a cmd_phy_on command is issued in the phy_off state followed quickly by a cmd_phy_ rx command. the cmd_phy_rx command is issued while fw_state is busy (that is, transitioning between the phy_off and phy_on states) but the cmd_ready bit is high, indicating that the command queue is empty. after the cmd_phy_rx command is issued, the cmd_ready bit transitions to a logic low, indicating that the command queue is full. after the phy_off to phy_on transition is finished, the phy_rx command is processed immediately by the communications processor, and the cmd_ready bit goes high, indicating that the command queue is empty and another command can be issued. transition radio from phy_off to phy_on waiting for command waiting for command 0xb2 = 0x12 (phy_on) 0xa0 0xb1 = 0x11 (phy_off) = 0x00 (busy) issue cmd_phy_on 0x80 cmd_ready fw_state status word communications processor action cs 09555-138 figure 62. operation of the cmd_ ready and fw_state bits in tran sitioning the adf7023- j from the phy_off state to the phy_on sta te transition radio from phy_on to phy_rx transition radio from phy_off to phy_on waiting for command waiting for command 0xb3 0xa0 0x80 0x80 0xa0 0xb1 = 0x11 (phy_off) = 0x00 (busy) = 0x13 (phy_rx) = 0x00 (busy) 0x12 issue cmd_phy_on issue cmd_phy_rx 0xb2 cmd_ready fw_state status word communications processor action cs in phy_on, reading new command 09555-139 figure 63. command queuing and operation of the cmd_ready and fw_state bits in transitioning the adf7023-j from the phy_off state to the phy_on state and then to the phy_rx state
adf7023-j rev. 0 | page 51 of 100 memory access memory locations are accessed by invoking the relevant spi command. an 11-bit address is used to identify registers or locations in the memory space. the most significant three bits of the address are incorporated into the spi command by appending them as the lsbs of the command word. figure 64 illustrates command, address, and data partitioning. the various spi memory access commands are different, depending on the memory location being accessed (see table 27 ). an spi command should be issued only if the spi_ready bit in the interrupt_source_1 register (address 0x337) of the status word bit is high. the adf7023-j interrupt handler can also be configured to generate an interrupt signal on irq_gp3 when the spi_ready bit is high. an spi command should not be issued while the communications processor is initializing (fw_state = 0x0f). spi commands can be issued in any other communications processor state, including the busy state (fw_state = 0x00). this allows the adf7023-j memory to be accessed while the radio is transi- tioning between states. block write mcr, bbram, and packet ram memory locations can be written to in block format using the spi_mem_wr command. the spi_mem_wr command code is 00011xxxb, where xxxb represent bits[10:8] of the first 11-bit address. if more than one data byte is written, the write address is automatically incremented for every byte sent until cs is set high, which terminates the memory access command (see for more details). the maximum block write for the mcr, packet ram, and bbram memories is 256 bytes, 256 bytes, and 64 bytes, respectively. these maximum block-write lengths should not be exceeded. figure 65 example wr ite 0x00 to the adc_config_high register (address 0x35a). ? t he first five bits of the spi_mem_wr command are 00011. ? t he 11-bit address of adc_config_high is 01101011010. ? t he first byte sent is 00011011 or 0x1b. ? t he second byte sent is 01011010 or 0x5a. ? the third byte sent is 0x00. thus, 0x1b, 0x5a, 0x00 is written to the part. cs mosi spi memory access command memory address bits[7:0] data byte 5 bits memory address bits[10:0] data n 8 bits 09555-029 figure 64. spi memory access command/address format table 27. summary of spi memory access commands spi command command value description spi_mem_wr 0x18 (packet ram), 0x19 (bbram), 0x1b (mcr), 0x1e (program ram) write data to bbram, mcr, or packet ram sequentially. an 11-bit address is used to identify memory locations. the most significant three bits of the address are incorporated into the command (xxxb). this command is followed by the remaining eight bits of the address. spi_mem_rd 0x38 (packet ram), 0x39 (bbram), 0x3b (mcr) read data from bbram, mcr, or packet ram sequentially. an 11-bit address is used to identify memory locations. the most significant three bits of the address are incorporated into the command (xxxb). this command is followed by the remaining eight bits of the address, which is subsequently followed by the appropriate number of spi_nop commands. spi_memr_wr 0x08 (packet ram), 0x09 (bbram), 0x0b (mcr) write data to bbram, mcr, or packet ram nonsequentially. spi_memr_rd 0x28 (packet ram), 0x29 (bbram), 0x2b (mcr) read data from bbram, mcr, or packet ram nonsequentially. spi_nop 0xff no operation. use for dummy writes when polling the status word. also used as dummy data on the mosi line when performing a memory read.
adf7023-j rev. 0 | page 52 of 100 random address write mcr, bbram, and packet ram memory locations can be written to in a nonsequential manner using the spi_memr_wr command. the spi_memr_wr command code is 00001xxxb, where xxxb represent bits[10:8] of the 11-bit address. the lower eight bits of the address should follow this command and then the data byte to be written to the address. the lower eight bits of the next address are entered, followed by the data for that address until all required addresses within that block are written, as shown in figure 66 . program ram write the program ram can be written to only by using the memory block write, as illustrated in figure 65 . spi_mem_wr should be set to 0x1e. see the downloadable firmware modules section for details on loading a firmware module to program ram. block read mcr, bbram, and packet ram memory locations can be read from in block format using the spi_mem_rd command. the spi_mem_rd command code is 00111xxxb, where xxxb represent bits[10:8] of the first 11-bit address. this command is followed by the remaining eight bits of the address to be read and then two spi_nop commands (dummy byte). the first byte available after writing the address should be ignored, with the second byte constituting valid data. if more than one data byte is to be read, the write address is automatically incremented for subsequent spi_nop commands sent. see figure 67 for more details. random address read mcr, bbram, and packet ram memory locations can be read from memory in a nonsequential manner using the spi_memr_rd command. the spi_memr_rd command code is 00101xxxb, where xxxb represent bits[10:8] of the 11-bit address. this command is followed by the remaining eight bits of the address to be written. each subsequent address byte is then written. the last address byte to be written should be followed by two spi_nop commands, as shown in figure 68 . the data bytes from memory, starting at the first address location, are available after the second status byte. example re ad the value stored in the adc_config_high register. ? t he first five bits of the spi_mem_rd command are 00111. ? th e 11-bit address of adc_config_high is 01101011010. ? th e first byte sent is 00111011 or 0x3b. ? th e second byte sent is 01011010 or 0x5a. ? t he third byte sent is 0xff (spi_nop). ? the fourth byte sent is 0xff. thus, 0x3b5affff is written to the part. the value shifted out on the miso line while the fourth byte is sent is the value stored in the adc_config_high register. mosi miso spi_mem_wr ignore address status data for [addr ess] status data for [address + 1] status data for [address + 2] status data for [address + n] status cs 09555-030 figure 65. memory (mcr, bbram, or packet ram) block write mosi miso spi_memr_wr ignore status status address 2 address 1 status data for [address 2] data for [address 1] status data for [address n] status cs 09555-142 figure 66. memory (mcr, bbram, or packet ram) random address write
adf7023-j rev. 0 | page 53 of 100 mosi miso ignore spi_mem_rd address spi_nop spi_nop spi_nop status status spi_nop max n = (256-initial address) cs data from address data from address + 1 data from address + n 09555-143 figure 67. memory (mcr, bbram, or packet ram) block read spi_memr_rd ignore status status data from address 1 data from address 2 data from address n data from address n ? 2 data from address n ? 1 address 1 address 2 address 3 address 4 address n spi_nop spi_nop mosi miso cs 09555-144 figure 68. memory (mcr, bbram, or packet ram) random address read
adf7023-j rev. 0 | page 54 of 100 low power modes the adf7023-j can be configured to operate in a broad range of energy sensitive applications where battery lifetime is critical. this includes support for applications where the adf7023-j is required to operate in a fully autonomous mode or applications where the host processor controls the transceiver during low power mode operation. these low power modes are implemented using a hardware wake-up controller (wuc), a firmware timer, and the smart wake mode functionality of the on-chip communications processor. the hardware wuc is a low power wuc that comprises a 16-bit wake-up timer with a programmable prescaler. the 32.768 khz rcosc or xosc provides the clock source for the timer. the firmware timer is a software timer residing on the adf7023-j. the firmware timer is used to count the number of wuc timeouts and can be used to count the number of adf7023-j wake-ups. the wuc and the firmware timer, therefore, provide a real-time clock capability. using the low power wuc and the firmware timer, the swm firmware allows the adf7023-j to wake up autonomously from sleep without intervention from the host processor. during this wake-up period, the adf7023-j is controlled by the communi- cations processor. this functionality allows carrier sense, packet sniffing, and packet reception while the host processor is in sleep, thereby dramatically reducing overall system current consumption. the smart wake mode can then wake the host processor on an interrupt condition. an overview of the low power mode configuration is shown in figure 69 , and the register settings that are used for the various low power modes are described in table 28 . table 28. settings for low power modes low power mode memory address register name bit description deep sleep modes 0x30d 1 wuc_config_low wuc_bbram_en 0: bbram contents are not retained during phy_sleep. 1: bbram contents are retained during phy_sleep. wuc 0x30c 1 wuc_config_high wuc_prescaler[2:0] sets the prescaler value of the wuc. wuc 0x30d 1 wuc_config_low wuc_rcosc_en enables the 32.768 khz rc osc. wuc 0x30d 1 wuc_config_low wuc_xosc32k_en enables the 32.768 khz external osc. wuc 0x30d 1 wuc_config_low wuc_clksel sets the wuc clock source. 1: rc osc selected. 2: xosc selected. wuc 0x30d 1 wuc_config_low wuc_arm enable to ensure that the device wakes from the phy_sleep state on a wuc timeout. wuc 0x30e 2 , wuc_value_high wuc_timer_value[15:0] the wuc timer value. 0x30f 2 wuc_value_low wuc interval(s) = wuc_timer_value 32,768 1) ( 2 + ler wuc_presca wuc 0x101 interrupt_mask_1 wuc_timeout enables the interrupt on a wuc timeout. firmware timer 0x100 interrupt_mask_0 interrupt_num_wakeups enabling this interrupt enables the firmware timer. interrupt is set when the number_of wakeups count exceeds the threshold. firmware timer 0x102, 0x103 number_of_wakeups_0 number_of_wakeups_1 number_of_wakeups[15:0] number of adf7023-j wake-ups. firmware timer 0x104, 0x105 number_of_wakeups_irq_ threshold_0 number_of_wakeups_irq_ threshold_1 number_of_wakeups_irq_ threshold[15:0] threshold for the number of adf7023-j wake-ups. when exceeded, the adf7023-j exits low power mode. swm 0x11a mode_control swm_en enables smart wake mode. swm 0x11a mode_control swm_rssi_qual enables rssi prequalification in smart wake mode.
adf7023-j rev. 0 | page 55 of 100 low power memory mode address register name bit description swm 0x108 swm_rssi_thresh swm_rssi_thresh[7:0] rssi threshold for rssi prequalification. rssi threshold (dbm) = swm_rssi_thresh ? 107. swm 0x107 parmtime_divider parmtime_divider[7:0] tick rate for the rx dwell timer. swm 0x106 rx_dwell_time rx_dwell_time[7:0] time that the adf7023-j remains awake during swm. receive dwell time = rx_dwell_time ivider parmtime_d 128 mhz6.5 swm 0x100 interrupt_mask_0 interrupt_swm_rssi_det interrupt_preamble_detect interrupt_sync_detect interrupt_address_match various interrupts that can be used in swm. 1 it is necessary to write to the 0x30c and 0x30d registers in the following order: wuc_config_high (address 0x30c), directly fo llowed by writing to wuc_config_low (address 0x30d). 2 it is necessary to write to the 0x30e and 0x30f registers in the following order: wuc_value_high (address 0x30e), directly fol lowed by writing to wuc_value_low (address 0x30f).
adf7023-j rev. 0 | page 56 of 100 set wuc_timeout interrupt phy_sleep bbram retained? wuc configured? increment number_of_wakeups set interrupt_num_ wakeups number_of_wakeups > threshold? swm enabled? (swm_en = 1) rssi qual enabled? (swm_rssi_qual) measure rssi rssi > threshold (swm_rssi_thresh) rssi int enabled? (interrupt_ swm_rssi_det) preamble detected? sync word detected? crc correct? address match? any interrupt set? time in rx > rx_dwell_time? set interrupt_ swm_rssi_det set interrupt_ num_wakeups set interrupt_ sync_detect set interrupt_ address_match wait for host command wait for host command wait for host command wait for host command wait for host command set interrupt_ crc_correct interrupt (if enabled) adf7023-j host no no no no no no no and rx_dwell_time exceeded no no no no no yes yes yes yes yes yes yes yes yes yes yes no yes yes yes yes yes yes smart wake mode smart wake mode (carrier sense only) wuc and rtc modes deep sleep mode 1 deep sleep mode 2 09555-145 figure 69. low power mode operation
adf7023-j rev. 0 | page 57 of 100 example low power modes deep sleep mode 2 deep sleep mode 2 is suitable for applications where the host processor controls the low power mode timing and the lowest possible adf7023-j sleep current is required. in this low power mode, the adf7023-j is in the phy_sleep state. the bbram contents are not retained. this low power mode is entered by issuing the cmd_hw_reset command from any radio state. to wake the part from the phy_sleep state, the cs pin should be set low. the initialization routine after a cmd_hw_reset command should be followed, as detailed in the section. radio control deep sleep mode 1 deep sleep mode 1 is suitable for applications where the host processor controls the low power mode timing and the adf7023-j configuration is retained during the phy_sleep state. in this low power mode, the adf7023-j is in the phy_sleep state with the bbram contents retained. before entering the phy_sleep state, the wuc_bbram_en bit (address 0x30d) should be set to 1 to ensure that the bbram is retained. this low power mode is entered by issuing the cmd_phy_sleep command from either the phy_off or phy_on state. to exit the phy_sleep state, the cs pin can be set low. the cs low initialization routine should then be followed, as detailed in the section. radio control wuc mode in this low power mode, the hardware wuc is used to wake the adf7023-j from the phy_sleep state after a user-defined duration. at the end of this duration, the adf7023-j can provide an interrupt to the host processor. while the adf7023-j is in the phy_sleep state, the host processor can optionally be in a deep sleep state to save power. before issuing the cmd_phy_sleep command, the host processor should configure the wuc and set the firmware timer threshold to zero (number_of_wakeups_irq_ threshold_x = 0, address 0x104 and address 0x105). the wuc_bbram_en bit (address 0x30d) should be set to 1 to ensure that the bbram is retained. on issuing the cmd_phy_ sleep command, the device goes to sleep for a period until the hardware timer times out. at this point, the device wakes up, and, if the wuc_timeout bit (address 0x101) or the interrupt_num_wakeups bit (address 0x100) interrupts are enabled, the device asserts the irq_gp3 pin. the operation of this low power mode is illustrated in figure 70 . wuc mode with firmware timer in this low power mode, the wuc is used to periodically wake the adf7023-j from the phy_sleep state, and the firmware timer is used to count the number of wuc timeouts. the combination of the wuc and the firmware timer provides a real-time clock (rtc) capability. the host processor should set up the wuc and the firmware timer before entering the phy_sleep state. the wuc_ bbram_en bit (address 0x30d) should be set to 1 to ensure that the bbram is retained. the wuc can be configured to time out at some standard time interval (for example, 1 sec, 60 sec). on issuing the cmd_phy_sleep command, the device enters the phy_sleep state for a period until the hardware timer times out. at this point, the device wakes up, increments the 16-bit firmware timer (number_of_wakeups_x, address 0x102 and address 0x103) and, if the wuc_timeout bit (address 0x101) is enabled, the device asserts the irq_gp3 pin. if the 16-bit firmware count is less than or equal to the user set threshold (number_of_wakeups_irq_threshold_x, address 0x104 and address 0x105), the device returns to the phy_sleep state. with this method, the firmware count (number_of_wakeups_x) equates to a real-time interval. when the firmware count exceeds the user-set threshold (number_of_wakeups_irq_threshold_x), the adf7023-j asserts the irq_gp3 pin, if the interrupt_num_ wakeups bit (address 0x100) is set, and enters the phy_off state. the operation of this low power mode is illustrated in figure 71 . smart wake mode (carrier sense only) in this low power mode, the wuc, firmware timer, and smart wake mode are used to implement periodic rssi measurements on a particular channel (that is, carrier sense). to enable this mode, the wuc and firmware timer should be configured before entering the phy_sleep state. the wuc_bbram_en bit (address 0x30d) should be set to 1 to ensure that the bbram is retained. the rssi measurement is enabled by setting the swm_rssi_qual bit = 1 and the swm_en bit = 1 (address 0x11a). the interrupt_swm_rssi_det bit (address 0x100) should also be enabled. if the measured rssi value is below the user-defined threshold set in the swm_rssi_thresh register (address 0x108), the device returns to the phy_sleep state. if the rssi measurement is greater than the swm_rssi_thresh value, the device sets the interrupt_swm_rssi_det interrupt to alert the host processor and waits in the phy_on state for a host command. the operation of this low power mode is illustrated in figure 72 .
adf7023-j rev. 0 | page 58 of 100 smart wake mode in this low power mode, the wuc, firmware timer, and smart wake mode are employed to periodically listen for packets. to enable this mode, the wuc and firmware timer should be configured and smart wake mode (swm) enabled (the swm_en bit, address 0x11a) before entering the phy_sleep state. the wuc_bbram_en bit (address 0x30d) should be set to 1 to ensure that the bbram is retained. rssi prequalification can be optionally enabled (swm_rssi_qual = 1, address 0x11a). when rssi prequalification is enabled, the adf7023-j begins searching for the preamble only if the rssi measurement is greater than the user-defined threshold. the adf7023-j is in the phy_rx state for a duration deter- mined by the rx_dwell_time setting (address 0x106). if the adf7023-j detects the preamble during the receive dwell time, it searches for the sync word. if the sync word routine is detected, the adf7023-j loads the received data to packet ram and checks for a crc and address match, if enabled. if any of the receive packet interrupts has been set, the adf7023-j returns to the phy_on state and waits for a host command. if the adf7023-j receives preamble detection during the receive dwell time but the remainder of the received packet extends beyond the dwell time, the adf7023-j extends the dwell time until all of the packet is received or the packet is recognized as invalid (for example, there is an incorrect sync word). this low power mode terminates when a valid packet interrupt is received. alternatively, this low power mode can be terminated via a firmware timer timeout. this can be useful if certain radio tasks (for example, ir calibration) or processor tasks must be run periodically while in the low power mode. the operation of this low power mode is illustrated in figure 73 . exiting low power mode as described in figure 69 , the adf7023-j waits for a host command on any of the termination conditions of the low power mode. it is also possible to perform an asynchronous exit from low power mode using the following procedure: 1. bring the cs pin of the spi low and wait until the miso output goes high. 2. issue a cmd_hw_reset command. the host processor should then follow the initialization procedure after a cmd_hw_reset command, as described in the initialization section.
adf7023-j rev. 0 | page 59 of 100 low power mode timing diagrams host: start wuc host: cmd_phy_sleep phy_off or phy_on adf7023-j operation interrupt wuc_timeout (if enabled) interrupt interrupt_num_wakeups (if enabled and number_of_wakeups_irq_threshold = 0) phy_sleep wuc timeout period phy_off 09555-146 figure 70. low power mode timing when using the wuc increment firmware timer increment firmware timer firmware timer > threshold host: cmd_phy_sleep host: start wuc phy_off or phy_on adf7023-j operation interrupt_ num_wakeups phy_sleep phy_sleep phy_sleep phy_off wuc timeout period wuc timeout period number_of_wakeups_irq_threshold real time internal 09555-147 figure 71. low power mode timing when using the wuc and the firmware timer host: cmd_phy_sleep host: start wuc phy_off or phy_on adf7023-j operation interrupt_ s wm_rssi_det phy_sleep rssi threshold rssi threshold rssi > threshold rssi rssi rssi phy_sleep phy_sleep phy_on wuc timeout period wuc timeout period 09555-148 figure 72. low power mode timing when using the wuc, firmware timer, and swm with carrier sense host: cmd_phy_sleep host: start wuc phy_off or phy_on adf7023-j operation interrupt_ swm_rssi_det interrupt_ preamble_detect interrupt_ sync_detect interrupt_ crc_correct interrupt_ address_match phy_sleep no packet detected no packet detected packet detected rx rx phy_sleep phy_sleep phy_on wuc timeout period wuc timeout period init phy_rx receive dwell time (rx_dwell_time) 09555-149 figure 73. low power mode timing when using the wuc, firmware timer, and swm
adf7023-j rev. 0 | page 60 of 100 wuc setup circuit description the adf7023-j features a low power wake-up controller comprising a 16-bit wake-up timer with a 3-bit programmable prescaler, as illustrated in figure 74 . the prescaler clock source can be configured to use either the 32.76 khz internal rc oscillator (rcosc) or the 32.76 khz external oscillator (xosc). this combination of programmable prescaler and 16-bit down counter gives a total hardware timer range of 30.52 s to 36.4 hours. configuration and operation th e hardware wuc is configured via the following registers: ? w uc_config_high (address 0x30c) ? wuc_config_low (address 0x30d) ? wuc_value_high (address 0x30e) ? wuc_value_low (address 0x30f) the relevant fields of each register are detailed in table 29 . all four of these registers are write only. t he wuc should be configured as follows: 1. clear all interrupts. 2. set required interrupts. 3. write to wuc_config_high and wuc_config_ low. ensure that the wuc_arm bit = 1. ensure that the wuc_bbram_en bit = 1 (retain bbram during phy_sleep). it is necessary to write to both registers together in the following order: wuc_config_high directly followed by writing to wuc_config_low. 4. write to wuc_value_high and wuc_value_low. this configures the wuc_timer_value[15:0] and, thus, the wuc timeout period. the timer begins counting from the configured value after these registers have been written to. it is necessary to write to both registers together in the following order: wuc_value_high directly followed by writing to wuc_value_low. adf7023-j wake-up circuit 16-bit down counter 16-bit reload value prescaler 32.768khz tick rate 1 0 rc oscillator 32khz xtal wuc wuc_config_low[4] wuc_value_high wuc_value_low to firmware timer wuc_config_high[2:0] wuc_timeout interrupt 09555-150 figure 74. hardware wake-up controller (wuc) table 29. wuc register settings wuc setting name description wuc_value_high [7:0] wuc_timer_value[15:8] wuc timer value. wuc interval(s) = wuc_timer_value 32,768 1) ( 2 + ler wuc_presca wuc_value_low[7:0] wuc_timer_value[7:0] wuc timer value. wuc_config_high[7:3] reserved set to 0. wuc_config_high[2:0] wuc_prescaler wuc_prescaler 32.768 khz divider tick period 000 1 30.52 s 001 4 122.1 s 010 8 244.1 s 011 16 488.3 s 100 128 3.91 ms 101 1034 31.25 ms 110 8192 250 ms 111 65,536 2000 ms
adf7023-j rev. 0 | page 61 of 100 wuc setting name description wuc_config_low[7] reserved set to 0. wuc_config_low[6] wuc_rcosc_en 1: enable. 0: disable rcosc32k. wuc_config_low[5] wuc_xosc32k_en 1: enable. 0: disable xosc32k. wuc_config_low[4] wuc_clksel 1: rc 32.768 khz oscillator. 0: external crystal oscillator. wuc_config_low [3] wuc_bbram_en 1: enable power to bbram during the phy_sleep state. 0: disable power to bbram during the phy_sleep state. wuc_config_low[2:1] reserved set to 0. wuc_config_low[0] wuc_arm 1: enable wake-up on wuc timeout event. 0: disable wake-up on wuc timeout event. firmware timer setup the adf7023-j wakes up from the phy_sleep state at the rate set by the wuc. a firmware timer, implemented by the on-chip processor, can be used to count the number of hardware wake-ups and generate an interrupt to the host processor. thus, the adf7023-j can be used to handle the wake-up timing of the host processor, reducing overall system power consumption. to set up the firmware timer, the host processor must set a value in the number_of_wakeups_irq_threshold[15:0] registers (address 0x104 and address 0x105). this 16-bit value represents the number of times the device wakes up before it interrupts the host processor. at each wake-up, the adf7023-j increments the number_of_wakeups[15:0] registers (address 0x102 and address 103). if this value exceeds the value set by the number_of_wakeups_irq_threshold[15:0] registers, the number_of_wakeups[15:0] value is cleared to 0. at this time, if the interrupt_num_wakeups bit in the interrupt_mask_0 register (address 0x100) is set, the device asserts the irq_gp3 pin and enters the phy_off state.
adf7023-j rev. 0 | page 62 of 100 downloadable firmware modules the program ram memory of the adf7023-j can be used to store firmware modules for the communications processor that provide the adf7023-j with extra functionality. the binary code for these firmware modules and details on their functionality are available from analog devices. these firmware modules are included in the applications software, which is available online at ftp://ftp.analog.com/pub/rfl/adf7023/ . three modules are briefly described in this section: image rejection calibration, aes encryption and decryption, and reed-solomon coding. writing a module to program ram t he sequence to write a firmware module to program ram is as follows: 1. ensure that the adf7023-j is in phy_off. 2. issue the cmd_ram_load_init command. 3. write the module to program ram using an spi memory block write (see the spi interface section). 4. issue the cmd_ram_load_done command. 5. issue the cmd_sync command. the firmware module is now stored on program ram. image rejection calibration module the calibration system initially disables the adf7023-j receiver, and an internal rf source is applied to the rf input at the image frequency. the algorithm then maximizes the receiver image rejection performance by iteratively minimizing the quadrature gain and phase errors in the polyphase filter. the calibration algorithm takes its initial estimates for quadrature phase correction (address 0x118) and quadrature gain correction (address 0x119) from bbram. after calibration, new optimum values of phase and gain are loaded back into these locations. these calibration values are maintained in bbram during sleep mode and are automatically reapplied from a wake-up event, which keeps the number of calibrations required to a minimum. depending on the initial values of quadrature gain and phase correction, the calibration algorithm can take approximately 20 ms to find the optimum image rejection performance. however, the calibration time can be significantly less than this when the seed values used for gain and phase correction are close to optimum. the image rejection performance is also dependent on temperature. to maintain optimum image rejection performance, a calibration should be activated whenever a temperature change of more than 10c occurs. the adf7023-j on-chip temperature sensor can be used to determine when the temperature exceeds this limit. to run the ir calibration, issue a cmd_ir_cal (register 0xbd). in order for this to work successfully, ensure that the bb filter calibration is enabled in the mode_control register (address 0x11a). aes encryption and decryption module the downloadable aes firmware module supports 128-bit block encryption and decryption with key sizes of 128 bits, 192 bits, and 256 bits. two modes are supported: ecb mode and cbc mode 1. ecb mode simply encrypts/decrypts on a 128-bit block by block with a single secret key as illustrated in figure 76 . cbc mode 1 encrypts after first adding (modulo 2), a 128-bit user- supplied initialization vector. the resulting cipher text is then used as the initialization vector for the next block and so forth, as illustrated in figure 77 . decryption provides the inverse functionality. the firmware also takes advantage of an on-chip hardware accelerator module to enhance throughput and minimize the latency of the aes processing. reed-solomon coding module this coding module uses reed-solomon block coding to detect and correct errors in the received packet. a transmit message of k bytes in length is appended with an error checking code (ecc) of length n ? k bytes to give a total message length of n bytes, as shown in figure 75 . n bytes k bytes (n ? k) bytes preamble sync word payload ecc 09555-151 figure 75. packet structure with appended reed-solomon ecc the receiver decodes the ecc to detect and correct up to t bytes in error, where t = (n ? k)/2. the firmware supports correction of up to five bytes in the n byte field. to correct t bytes in error, an ecc length of 2t bytes is required, and the byte errors can be randomly distributed throughout the payload and ecc fields. reed-solomon coding exhibits excellent burst error correction capability and is commonly used to improve the robustness of a radio link in the presence of transient interference or due to rapid signal fading conditions that can corrupt sections of the message payload. reed-solomon coding is also capable of improving the receivers sensitivity performance by several db, where random errors tend to dominate under low snr conditions and the receivers packet error rate performance is limited by thermal noise. the number of consecutive bit errors that can be 100% corrected is {(t ? 1) 8 + 1}. longer, random bit-error patterns, up to t bytes, can also be corrected if the error patterns start and end at byte boundaries. the firmware also takes advantage of an on-chip hardware accelerator module to enhance throughput and minimize the latency of the reed-solomon processing.
adf7023-j rev. 0 | page 63 of 100 128 bits 128 bits aes encrypt key 128 bits 128 bits aes encrypt key 128 bits 128 bits aes encrypt key plain text c ipher text ecb mode 09555-152 figure 76. ecb mode initial vector plain text cipher text cbc mode 1 128 bits 128 bits aes encrypt key + 128 bits 128 bits aes encrypt key + 128 bits 128 bits aes encrypt key + 128 bits 128 bits aes encrypt key + 09555-153 figure 77. cbc mode 1
adf7023-j rev. 0 | page 64 of 100 radio blocks frequency synthesizer a fully integrated rf frequency synthesizer is used to generate both the transmit signal and the receivers local oscillator (lo) signal. the architecture of the frequency synthesizer is shown in figure 78 . the receiver uses a fractional-n frequency synthesizer to generate the mixers lo for down conversion to the intermediate frequency (if) of 200 khz or 300 khz. in transmit mode, a high resolution sigma-delta (-) modulator is used to generate the required frequency deviations at the rf output when fsk data is trans- mitted. to reduce the occupied fsk bandwidth, the transmitted bit stream can be filtered using a digital gaussian filter, which is enabled via the radio_cfg_9 register (address 0x115). the gaussian filter uses a bandwidth time (bt) of 0.5. the vco and the pll loop filter of the adf7023-j are fully integrated. to reduce the effect of pulling of the vco by the power-up of the pa and to minimize spurious emissions, the vco operates at twice the rf frequency. the vco signal is then divided by 2, giving the required frequency for the transmitter and the required lo frequency for the receiver. a high speed, fully automatic calibration scheme is used to ensure that the frequency and amplitude characteristics of the vco are maintained over temperature, supply voltage, and process variations. the calibration is automatically performed when the cmd_phy_rx or the cmd_phy_tx command is issued. the calibration duration is 142 s, and if required, the calibration_status register (address 0x339) can be polled to indicate the completion of the vco self calibration. after the vco is calibrated, the frequency synthesizer settles to within 5 ppm of the target frequency in 56 s. f_deviation rf freq loop filter vco 26mhz ref tx dat a frac-n integer-n n divider vco calibration - ? divider gaussian filter pfd charge pump 2 2 09555-035 figure 78. rf frequency synthesizer architecture synthesizer bandwidth the synthesizer loop filter is fully integrated on chip and has a programmable bandwidth. the communications processor automatically sets the bandwidth of the synthesizer when the device enters the phy_tx or the phy_rx state. upon entering the phy_tx state, the communications processor chooses the band- width based on the programmed modulation scheme (2fsk or gfsk) and the data rate. this ensures optimum modulation quality for each data rate. upon entering the phy_rx state, the communications processor sets a narrow bandwidth to ensure best receiver rejection. in all, there are eight bandwidth configurations. each synthesizer bandwidth setting is described in table 30 . table 30. automatic synthesizer bandwidth selections description data rate (kbps) closed-loop synthesizer bandwidth (khz) rx 2fsk/gfsk/msk/gmsk all 92 tx 2fsk/gfsk/msk/gmsk 1 to 49.5 130 tx 2fsk/gfsk/msk/gmsk 49.6 to 99.1 174 tx 2fsk/gfsk/msk/gmsk 99.2 to 129.5 174 tx 2fsk/gfsk/msk/gmsk 129.6 to 179.1 226 tx 2fsk/gfsk/msk/gmsk 179.2 to 239.9 305 tx 2fsk/gfsk/msk/gmsk 240 to 300 382 for performance margin to the t96 specification limits, the pll closed-loop bandwidth is optimized depending on the data rate. the following procedure must be used to program the device for optimized pll bandwidth settings during transmit operation. a s part of the initial bbram configuration, do the following: x issue the spi_mem_wr command, writing 0x2 to bits[5:4] of register 0x113 (radio_cfg_7). x issue the cmd_config_dev command. the custom transmit lut must be written to the 0x010 to 0x018 packet ram locations. this is achieved using a spi_mem_wr command and a block write as described in the memory access section. the lut values are described in table 31 . these values are retained in memory while vddbat remains valid, unless phy_sleep is entered; in which case, the values must be reprogrammed. table 31. t96 custom transmit look-up table (lut) register data rate = 50 kbps or 100 kbps (clbw = 130 khz) data rate = 200 kbps (clbw = 223 khz) 0x010 0x10 0x20 0x011 0x10 0x20 0x012 0x0f 0x0f 0x013 0x0f 0x0f 0x014 0x1f 0x1f 0x015 0x0f 0x05 0x016 0x1f 0x1f 0x017 0x33 0x33 0x018 0x22 0x18
adf7023-j rev. 0 | page 65 of 100 synthesizer settling after the vco calibration, a 56 s delay is allowed for synthesizer settling. this delay is fixed at 56 s by default and ensures that the synthesizer has fully settled when using any of the default synthesizer bandwidths. however, in some cases, it may be necessary to use a custom synthesizer settling delay. to use a custom delay, set the custom_ trx_synth_lock_time en bit to 1 in the mode_control register (address 0x11a). the synthesizer settling delays for the phy_rx and the phy_tx state transitions can be set independently in the rx_synth_lock_time register (address 0x13e) and the tx_synth_lock_time register (address 0x13f). the settling time can be set in the 2 s to 512 s range in steps of 2 s. bypassing vco calibration it is possible to bypass the vco calibration for ultrafast frequency hopping in transmit or receive. the calibration data for each rf channel should be stored in the host processor memory. the calibration data comprises two values: the vco band select value and the vco amplitude level. r ead and store calibration data 1. go to the phy_tx or the phy_rx state without bypassing the vco calibration. 2. read the following mcr registers and store the calibrated data in memory on the host processor: a. vco_band_readback (address 0x3da) b. vco_ampl_readback (address 0x3db) b ypassing vco calibration on cmd_phy_tx or cmd_phy_rx 1. ensure that the bbram is configured. 2. set vco_ovrw_en (address 0x3cd) = 0x3. 3. set vco_cal_cfg (address 0x3d0) = 0x0f. 4. set vco_band_ovrw_val (address 0x3cb) = stored vco_band_readback (address 0x3da) for that channel. 5. set vco_ampl_ovrw_val (address 0x3cc) = stored vco_ampl_readback (address 0x3db) for that channel. 6. set synth_cal_en = 0 (in the calibration_ control register, address 0x338). 7. set synth_cal_en = 1 (in the calibration_ control register, address 0x338). 8. issue cmd_phy_tx or cmd_phy_rx to go to the phy_tx or phy_rx state without the vco calibration. crystal oscillator a 26 mhz crystal oscillator operating in parallel mode must be connected between the xosc26p and xosc26n pins. two parallel loading capacitors are required for oscillation at the correct frequency. their values are dependent upon the crystal specification. they should be chosen to ensure that the shunt value of capacitance added to the pcb track capacitance and the input pin capacitance of the adf7023-j equals the specified load capacitance of the crystal, usually 10 pf to 20 pf. track capacitance values vary from 2 pf to 5 pf, depending on board layout. the total load capacitance is described by c load = pcb pin c c c2c1 ++ + 2 11 1 where: c load is the total load capacitance. c1 and c2 are the external crystal load capacitors. c pin is the adf7023-j input capacitance of the xosc26p and xosc26n pins and is equal to 2.1 pf. c pcb is the pcb track capacitance. when possible, choose capacitors that have a very low temperature coefficient to ensure stable frequency operation over all conditions. the crystal frequency error can be corrected by means of an integrated digital tuning varactor. for a typical crystal load capacitance of 10 pf, a tuning range of ?15 ppm to +11.25 ppm is available via programming of a 3-bit dac, according to table 32 . the 3-bit value should be written to the xosc_cap_dac bits in the osc_config register (address 0x3d2). alternatively, any error in the rf frequency due to crystal error can be adjusted for by offsetting the rf channel frequency using the rf channel frequency setting in bbram memory. table 32. crystal frequency pulling programming xosc_cap_dac pulling (ppm) 000 +15 001 +11.25 010 +7.5 011 +3.75 100 0 101 ?3.75 110 ?7.5 111 ?11.25 modulation the adf7023-j supports binary frequency shift keying (2fsk), minimum shift keying (msk), binary level gaussian filtered 2fsk (gfsk), and gaussian filtered msk (gmsk). the desired transmit and receive modulation formats are set in the radio_cfg_9 register (address 0x115). when using 2fsk/gfsk/msk/gmsk modulation, the frequency deviation can be set using the freq_deviation[11:0] bits in the radio_cfg_1 register (address 0x10d) and the radio_cfg_2 register (address 0x10e). the data rate can be set in the 1 kbps to 300 kbps range using the data_rate[11:0] parameter in the radio_cfg_0 register (address 0x10c) and radio_cfg_1 register (address 0x10d). for gfsk/gmsk modulation, the gaussian filter uses a fixed bt of 0.5.
adf7023-j rev. 0 | page 66 of 100 rf output stage power amplifier (pa) the adf7023-j pa can be configured for single-ended or differential output operation using the pa_single_diff_sel bit in the radio_cfg_8 register (address 0x114). the pa level is set by the pa_level bit in the radio_cfg_8 register and has a range of 0 to 15. for finer control of the output power level, the pa_level_mcr register (address 0x307) can be used. it offers more resolution with a setting range of 0 to 63. the relationship between the pa_level and pa_level_mcr settings is given by pa_level_mcr = 4 pa_level + 3 the single-ended configuration can deliver 13.5 dbm output power. the differential pa can deliver 10 dbm output power and allows a straightforward interface to dipole antennae. the two pa configurations offer a tx antenna diversity capability. note that the two pas cannot be enabled at the same time. automatic pa ramp the adf7023-j has built-in up a nd down pa ramping for both single-ended and differential pas. there are eight ramp rate settings, with the ramp rate defined as a certain number of pa power level settings per data bit period. the pa_ramp variable in the radio_cfg_8 register (address 0x114) sets this pa ramp rate, as illustrated in figure 79 . data bits pa ramp 1 (256 codes per bit) pa ramp 2 (128 codes per bit) pa ramp 3 (64 codes per bit) pa ramp 4 (32 codes per bit) pa ramp 5 (16 codes per bit) pa ramp 6 (8 codes per bit) pa ramp 7 (4 codes per bit) 1 2 3 4 ... 8 ... 16 09555-036 figure 79. pa ramp for different pa_ramp settings the pa ramps to the level set by the pa_level or pa_level_ mcr settings. enabling the pa ramp reduces spectral splatter and helps meet radio regulations, which limit pa transient spurious emissions. to ensure optimum performance, an adequately long pa ramp rate is required based on the data rate and the pa output power setting. the pa_ramp setting should, therefore, be set such that ramp rate ( codes / bit ) < 2500 ]0:11[ ]0:5[ data_rate cr pa_level_m where pa_level_mcr is related to the pa_level setting by pa_level_mcr = 4 pa_level + 3. pa/lna interface the adf7023-j supports both single-ended and differential pa outputs. only one pa can be active at a time. the differential pa and lna share the same pins, rfio_1p and rfio_1n, which facilitate a simpler antenna interface. the single-ended pa output is available on the rfo2 pin. a number of pa/lna antenna matching options are possible and are described in the pa/lna matching section. receive channel filter the channel filter of the receiver is a fourth-order, active polyphase butterworth filter with programmable bandwidths of 100 khz, 150 khz, 200 khz, and 300 khz. the fourth-order filter gives very good interference suppression of adjacent and neighboring channels and also suppresses the image channel by approximately 36 db at a 100 khz if bandwidth and an rf frequency of 915 mhz. for channel bandwidths of 100 khz to 200 khz, an if frequency of 200 khz is used, which results in an image frequency located 400 khz below the wanted rf frequency. when the 300 khz bandwidth is selected, an if frequency of 300 khz is used, and the image frequency is located at 600 khz below the wanted frequency. the bandwidth and center frequency of the if filter are calibrated automatically after entering the phy_on state if the bb_cal bit is set in the mode_control register (address 0x11a). the filter calibration time takes 100 s. the if bandwidth is programmed by setting the ifbw field in the radio_cfg_9 register (address 0x115). the filters pass band is centered at an if frequency of 200 khz when bandwidths of 100 khz to 200 khz are used and centered at 300 khz when an if bandwidth of 300 khz is used. image channel rejection the adf7023-j is capable of providing improved receiver image rejection performance by the use of a fully integrated image rejection calibration system under the control of the on-chip communications processor. to op erate the calibration system, a firmware module is downloaded to the on-chip program ram. the firmware download is supplied by analog devices and described in the downloadable firmware modules section. automatic gain control (agc) agc is enabled by default and keeps the receiver gain at the correct level by selecting the lna, mixer, and filter gain settings based on the measured rssi level. the lna has three gain levels, the mixer has two gain levels, and the filter has three gain levels. in all, there are six agc stages, which are defined in table 33 . table 33. agc gain modes gain mode lna gain mixer gain filter gain 1 high high high 2 high low high 3 medium low high 4 low low high 5 low low medium 6 low low low
adf7023-j rev. 0 | page 67 of 100 rssi method 2 the agc remains at each gain stage for a time defined by the agc_clk_divide register (address 0x32f). the default value of agc_clk_divide = 0x28 gives an agc delay of 25 s. when the rssi is above agc_high_threshold (address 0x35f), the gain is reduced. when the rssi is below agc_low_threshold (address 0x35e) , the gain is increased. the cmd_get_rssi command can be used from the phy_on state to read the rssi. this rssi measurement method uses additional low-pass filtering, resulting in a more accurate rssi reading. the rssi result is loaded to the rssi_readback register (address 0x312) by the communications processor. the rssi_readback register contains a twos complement value and can be converted to input power in dbm using the following formula: the agc can be configured to remain active while in the phy_rx state or can be locked on preamble detection. the agc can also be set to manual mode, in which case, the host processor must set the lna, filter, and mixer gains by writing to the agc_mode register (address 0x35d). the agc operation is set by the agc_lock_mode setting in the radio_cfg_7 register (address 0x113) and is described in table 34 . rssi(dbm) = rssi_readback C 107 the cmd_get_rssi execution time is specified in table 11 . rssi method 3 th is method supports the measurement of rssi by the host processor at any time while in the phy_rx state. the receiver input power can be calculated using the following procedure: the lna, filter, and mixer gains can be read back through the agc_gain_status register (address 0x360). table 34. agc operation agc_lock_mode bits in radio_ cfg_7 register 1. set agc to hold by setting the agc_mode register (address 0x35d) = 0x40 (only necessary if agc has not been locked on the preamble or sync word). description 0 agc is free running. 2. read back the agc gain settings (agc_gain_status register, address 0x360). 1 agc is disabled. gains must be set manually. 3. read the adc_readback[7:0] bit values (address 0x327 and address 0x328; see the analog-to-digital converter section). 2 agc is held at the current gain level. 3 agc is locked on preamble detection. rssi 4. re-enable the agc by setting the agc_mode register (address 0x35d) = 0x00 (only necessary if agc has not already been locked on the preamble or sync word). the rssi is based on a successive compression, log amplifier architecture following the analog channel filter. the analog rssi level is digitized by an 8-bit sar adc for user readback and for use by the digital agc controller. 5. calculate the rssi in dbm as follows: rssi(dbm) = 109 7 1 ? ? ? ? ? ? ? + ction gain_corre ck[7:0] adc_readba the adf7023-j has three rssi measurement functions that support a wide range of applications. these functions can be used to implement carrier sense (cs) or clear channel assessment (cca). in packet mode, the rssi is automatically recorded in mcr memory and is available for user readback after receipt of a packet. where gain_correction is determined by the value of the agc_gain_status register (address 0x360) as shown in table 35 . table 36 details the three rssi measurement methods. table 35. gain mode correction for 2fsk/gfsk/msk/gmsk rssi agc_gain_status (address 0x360) rssi method 1 when a valid packet is received in packet mode, the rssi level during postamble is automatically loaded to the rssi_readback register (address 0x312) by the communications processor. the rssi_readback register contains a twos complement value and can be converted to input power in dbm using the following formula: gain_correction 0x00 44 0x01 35 0x02 26 0x0a 17 0x12 10 rssi(dbm) = rssi_readback ? 107 0x16 0 to extend the linear range of rssi measurement down to an input power of ?110 dbm (see figure 42 ), a cosine adjustment can be applied using the following formula: to simplify the rssi calculation, the following approximation can be used by the host processor: 7 1 8 1 ? ? ? ? ? ? ++ 64 1 8 1 1 rssi(dbm) = cos ? ? ? ? ? ? readback rssi _ 8 rssi_readback ? 106 where cos(x) is the cosine of angle x (radians).
adf7023-j rev. 0 | page 68 of 100 table 36. summary of rssi measurement methods rssi method rssi type modulation available in packet mode available in sport mode description 1 automatic end of packet rssi 2fsk/gfsk/ msk/gmsk yes no automatic rssi measurement during reception of the postamble in packet mode. the rssi result is available in the rssi_readback register (address 0x312). 2 cmd_get_rssi command from phy_on 2fsk/gfsk/ msk/gmsk yes yes automatic rssi measurement from phy_on using cmd_get_rssi. the rssi result is available in the rssi_readback register (address 0x312). 3 rssi via adc and agc readback, fsk 2fsk/gfsk/ msk/gmsk yes yes rssi measurement based on the adc and agc gain read backs. the host processor calculates rssi in dbm.
adf7023-j rev. 0 | page 69 of 100 frequency correlator if filter limiters mixer rfio_1p rfio_1n lna rxdata/ rxclk post-demod filter clock and data recovery i q if rf synthesizer (lo) data_rate[11:0] post_demod_bw[7:0] discrim_bw[7:0] discrim_phase[1:0] ifbw[1:0] (addr ess radio_cfg_9[7:6]) pi control 2 t averaging filter afc system range max_afc_range[7:0] afc_lock_mode[1:0] afc_ki[3:0] (addr ess radio_cfg_11[7:4]) afc_kp[3:0] afc lock sport mode gpios communications processor preamble detect sync word detect preamble_match = 0 09555-156 figure 80. 2fsk/gfsk/msk/gmsk demodulation and afc architecture 2fsk/gfsk/msk/gmsk demodulation a correlator demodulator is used for 2fsk, gfsk, msk, and gmsk demodulation. the quadrature outputs of the if filter are first limited and then fed to a digital frequency correlator that performs filtering and frequency discrimination of the 2fsk/gfsk/msk/ gmsk spectrum. data is recovered by comparing the output levels from two correlators. the performance of this frequency discriminator approximates that of a matched filter detector, which is known to provide optimum detection in the presence of additive white gaussian noise (awgn). this method of 2fsk/gfsk/msk/ gmsk demodulation provides approximately 3 db to 4 db better sensitivity than a linear frequency discriminator. the 2fsk/gfsk/ msk/gmsk demodulator architecture is shown in figure 80 . the adf7023-j is configured for 2fsk/gfsk/msk/gmsk demodulation by setting demod_scheme = 0 in the radio_cfg_9 register (address 0x115). to optimize receiver sensitivity, the correlator bandwidth and phase must be optimized for the specific deviation frequency, data rate, and maximum expected frequency error between the transmitter and receiver. the bandwidth and phase of the discriminator must be set using the discrim_bw bits in the radio_cfg_3 register (address 0x10f) and the discrim_ phase[1:0] bits in the radio_cfg_6 register (address 0x112). the discriminator setup is performed in three steps. step 1: calculate the discriminator bandwidth coefficient k the discriminator bandwidth coefficient k depends on the modulation index (mi), which is determined by ratedata de v fsk mi _2 = where fsk_dev is the 2fsk/gfsk/msk/gmsk frequency deviation in hertz (hz), measured from the carrier to the +1 symbol frequency (positive frequency deviation) or to the ?1 symbol frequency (negative frequency deviation). data rate is the data rate in bits per second (bps). the value of k is then determined by mi 1, afc off : k = floor ? ? ? ? ? ? _ _ mi < 1, afc off : k = floor ? ? ? ? ? ? ? ? ? ? 2 _ ratedata freqif mi 1, afc on : k = floor ? ? ? ? ? ? ? ? + __ _ _ mi < 1, afc on : k = floor ? ? ? ? ? ? ? ? ? ? + __ 2 _ where: mi is the modulation index. k is the discriminator coefficient. floor[x] is a function to round down to the nearest integer. if_freq is the if frequency in hertz (200 khz or 300 khz). fsk_dev is the 2fsk/gfsk/msk/gmsk frequency deviation in hertz. freq_error_max is the maximum expected frequency error, in hertz, between tx and rx. step 2: calculate the discrim_bw setting the bandwidth setting of the discriminator is calculated based on the discriminator coefficient k and the if frequency. the bandwidth is set using the discrim_bw[7:0] setting (address 0x10f), which is calculated according to discrim_bw[7:0] = round ? ? ? ? ? ? _ 25.3
adf7023-j rev. 0 | page 70 of 100 step 3: calculate the discrim_phase setting the phase setting of the discriminator is calculated based on the discriminator coefficient k, as described in table 37 . the phase is set using the discrim_phase[1:0] value in the radio_cfg_6 register (address 0x112). table 37. setting the discrim_phase[1:0] values based on k k k/2 (k + 1)/2 discrim_phase[1:0] even odd 0 odd even 1 even even 2 odd odd 3 afc the adf7023-j features an internal real-time automatic frequency control loop. in receive mode, the control loop automatically monitors the frequency error during the packet preamble sequence and adjusts the receiver synthesizer local oscillator using proportional integral (pi) control. the afc frequency error measurement bandwidth is targeted specifically at the packet preamble sequence (dc free). afc is supported during 2fsk/gfsk/msk/gmsk demodulation. afc can be configured to lock on detection of the qualified preamble or on detection of the qualified sync word. to lock afc on detection of the qualified preamble, set afc_lock_ mode = 3 (address 0x116) and ensure that preamble detection is enabled in the preamble_match register (address 0x11b). afc lock is released if the sync word is not detected immediately after the end of the preamble. in packet mode, if the qualified preamble is followed by a qualified sync word, the afc lock is maintained for the duration of the packet. in sport mode, the afc lock is released on transitioning back to the phy_on state or when a cmd_phy_rx is issued while in the phy_rx state. to lock afc on detection of the qualified sync word, set afc_lock_mode = 3 and ensure that preamble detection is disabled in the preamble_match register (address 0x11b). if this mode is selected, consideration must be given to the selection of the sync word. the sync word should be dc free and have short run lengths yet low correlation with the preamble sequence. see the sync word description in the packet mode section for further details. after lock on detection of the qualified sync word, the afc lock is maintained for the duration of the packet. in sport mode, the afc lock is released on transitioning back to the phy_on state or when cmd_ phy_rx is issued while in the phy_rx state. afc is enabled by setting the afc_lock_mode bits in the radio_cfg_10 register (address 0x116), as described in table 38 . table 38. afc mode afc_lock_mode [1:0] mode 0 free running: afc is free running. 1 disabled: afc is disabled. 2 hold: afc is paused. 3 lock: afc locks after the preamble or sync word. the bandwidth of the afc loop can be controlled by the afc_ki and afc_kp bits in the radio_cfg_11 register (address 0x117). the maximum afc pull-in range is automatically set based on the programmed if filter bandwidth (the ifbw bits in the radio_cfg_9 register (address 0x115). table 39. maximum afc pull-in range if bandwidth (khz) max afc pull-in range (khz) 100 50 150 75 200 100 300 150 afc and preamble length the afc requires a certain number of the received preamble bits to correct the frequency error between the transmitter and the receiver. the number of preamble bits required depends on the data rate and whether the afc is locked on detection of the qualified preamble or locked on detection of the qualified sync word. this is discussed in more detail in the recommended receiver settings for 2fsk/gfsk/msk/gmsk section. afc readback the frequency error between the received carrier and the receiver local oscillator can be measured when afc is enabled. the error value can be read from the frequency_error_readback register (address 0x372), where each lsb equates to 1 khz. the value is a twos complement number. the frequency_error_ readback value is valid in the phy_rx state after the afc has been locked. the value is retained in the frequency_ error_readback register after recovering a packet and transitioning back to the phy_on state. post-demodulator filter a second-order, digital low-pass filter removes excess noise from the demodulated bit stream at the output of the discriminator. the bandwidth of this post-demodulator filter is programmable and must be optimized for the users data rate and received modulation type. if the bandwidth is set too narrow, performance degrades due to inter-symbol interference (isi). if the bandwidth is set too wide, excess noise degrades the performance of the receiver. for optimum performance, the post-demodulator filter bandwidth should be set close to 0.75 times the data rate (when using fsk/gfsk/msk/gmsk modulation). the actual bandwidth of the post-demodulator filter is given by post-demodulator filter bandwidth (khz) = post_demod_bw 2 where post_demod_bw is set in the radio_cfg_4 register (address 0x110).
adf7023-j rev. 0 | page 71 of 100 clock recovery an oversampled digital clock and data recovery (cdr) pll is used to resynchronize the received bit stream to a local clock in all modulation modes. the maximum symbol rate tolerance of the cdr pll is determined by the number of bit transitions in the transmitted bit stream. for example, during reception of a 010101 preamble, the cdr achieves a maximum data rate tolerance of 3.0%. however, this tolerance is reduced during recovery of the remainder of the packet where symbol transitions may not be guaranteed to occur at regular intervals during the payload data. to maximize data rate tolerance of the receivers cdr, 8b/10b encoding or manchester encoding should be enabled, which guarantees a maximum number of contiguous bits in the transmitted bit stream. data whitening can also be enabled on the adf7023-j to break up long sequences of contiguous data bit patterns. using 2fsk/gfsk/msk/gmsk modulation, it is also possible to tolerate uncoded payload data fields and payload data fields with long run length coding constraints if the data rate tolerance and packet length are both constrained. more details of cdr operation using uncoded packet formats are discussed in the an-915 application note. the cdr pll of the adf7023-j is optimized for fast acquisition of the recovered symbols during preamble and typically achieves bit synchronization within five symbol transitions of preamble. recommended receiver settings for 2fsk/gfsk/msk/gmsk to optimize the adf7023-j receiver performance and to ensure the lowest possible packet error rate, it is recommended to use the following configurations: ? s et the recommended agc low and high thresholds and the agc clock divide. ? s et the recommended afc ki and kp parameters. ? use a preamble length the minimum recommended preamble length. ? when the agc is configured to lock on the sync word at data rates greater than 200 kbps, it is recommended to set the sync word error tolerance to one bit. the recommended settings for agc, afc, preamble length, and sync word are summarized in table 41 . recommended agc settings t o optimize the receiver for robust packet error rate performance, when using minimum preamble length over the full input power range, it is recommended to overwrite the default agc settings in the mcr memory. the recommended settings are as follows: ? a gc_high_threshold (address 0x35f) = 0x78 ? agc_low_threshold (address 0x35e) = 0x46 ? agc_clk_divide (address 0x32f) = 0x0f or 0x19 (depends on the data rate; see table 41 ) mcr memory is not retained in phy_sleep; therefore, to allow the use of these optimized agc settings in low power mode applications, a static register fix can be used. an example static register fix to write to the agc settings in mcr memory is shown in tabl e 40 . note that the accuracy of the rssi readback is degraded with these modified settings. table 40. example static register fix for agc settings bbram register data description 0x128 (static_reg_fix) 0x2b pointer to bbram address 0x12b 0x12b 0x5e mcr address 0x35e 0x12c 0x46 data to write to mcr address 0x35e (sets agc low threshold) 0x12d 0x5f mcr address 0x35f 0x12e 0x78 data to write to mcr address 0x35f (sets agc high threshold) 0x12f 0x2f mcr address 0x32f 0x130 0x0f data to write to mcr address 0x32f (sets agc clock divide) 0x131 0x00 ends static mcr register fixes recommended afc settings the bandwidth of the afc loop is controlled by the afc_ki and afc_kp bits in the radio_cfg_11 register (address 0x117). to ensure optimum afc accuracy while minimizing the afc settling time (and thus the re quired preamble length), the afc_ki and afc_kp bits should be set as outlined in table 4 1 . recommended preamble length when afc is locked on preamble detection, the minimum preamble length is between 40 bits and 60 bits depending on the data rate. when afc is set to lock on sync word detection, the minimum preamble length is between 14 bits and 32 bits, depending on the data rate. when afc and preamble detection are disabled, the minimum preamble length is dependent on the agc settling time and the cdr acquisition time and is between 8 bits and 24 bits, depending on the data rate. the required preamble length for various data rates and receiver configurations is summarized in table 41 . recommended sync word tolerance at data rates greater than 200 kbps and when the agc is configured to lock on the sync word, it is recommended to set the sync word error tolerance to one bit (sync_error_tol = 1). this prevents an agc gain change during sync word reception causing a packet loss by allowing one bit error in the received sync word.
adf7023-j rev. 0 | page 72 of 100 table 41. summary of recommended agc, afc, preamble length, and sync word error tolerance for 2fsk/gfsk/msk/gmsk agc 2 afc 3 data rate (kbps) frequency deviation (khz) if bw (khz) afc pull-in range (khz) setup 1 high threshold low threshold clock divide on/off ki kp minimum preamble length (bits) 4 sync word error tolerance (bits) 5 1 0x78 0x46 0x0f on 7 3 64 0 2 0x78 0x46 0x19 on 8 3 32 1 300 75 300 150 3 0x78 0x46 0x19 off 24 1 200 50 200 100 1 0x78 0x46 0x19 on 7 3 58 0 150 37.5 150 75 1 0x78 0x46 0x19 on 7 3 54 0 100 25 100 50 1 0x78 0x46 0x19 on 7 3 52 0 50 12.5 100 50 1 0x78 0x46 0x19 on 7 3 50 0 1 0x78 0x46 0x19 on 7 3 44 0 2 0x78 0x46 0x19 on 7 3 14 0 38.4 20 100 50 3 0x78 0x46 0x19 off 8 0 1 0x78 0x46 0x19 off 8 0 9.6 10 100 50 1 0x78 0x46 0x19 on 7 3 46 0 1 0x78 0x46 0x19 off 8 0 1 10 100 50 1 0x78 0x46 0x19 on 7 3 40 0 1 setup 1: afc and agc are configured to lock on preamble de tection by setting afc_lock_mode = 3 and agc_lock_mode = 3. setup 2: afc and agc are configured to lock on sync word detect ion by setting afc_lock _mode = 3, agc_lock_mode = 3, and preambl e_match = 0. setup 3: afc is disabl ed and agc is configured to lock on sync word detection by setting af c_lock_mode = 1, agc_lock_mode = 3, and preamble_match = 0. for setup 2 and setup 3, sync word leng th is 24 bits. sync word detect length has an impact on minimum preamble length. 2 the agc high threshold is configured by writing to the agc_high_threshold register (address 0x35f). the agc low threshold is c onfigured by writing to the agc_low_threshold register (address 0x35e). the agc clock divide is configured by writ ing to the agc_clk_divide register (addre ss 0x32f). note that the accuracy of the rssi readback is degraded with these modified agc threshold settings. 3 the afc is enabled or disabled by writing to the afc_lock_mode setting in register radio_cfg_10 (address 0x116). the afc ki an d kp parameters are configured by writing to the afc_kp and afc_ki settings in the radio _cfg_11 register (address 0x117). 4 the transmit preamble length (in bytes) is set by writing to the preamble_len register (address 0x11d). 5 the sync word error tolerance (in bits) is set by writing to the sync_error_tol setting in the sync_control register (address 0x120).
adf7023-j rev. 0 | page 73 of 100 peripheral features analog-to-digital converter the adf7023-j supports an integrated sar adc for digitization of analog signals that include the analog temperature sensor, the analog rssi level, and an external analog input signal (pin 30). the conversion time is typically 1 s. the result of the conversion can be read from the adc_readback_high register (address 0x327), and the adc_readback_low register (address 0x328). the adc readback is an 8-bit value. the signal source for the adc input is selected via the adc_config_low register (address 0x359). in the phy_rx state, the source is automatically set to the analog rssi. the adc is automatically enabled in phy_rx. in other radio states, the host processor must enable the adc by setting powerdown_rx (address 0x324) = 0x10. to perform an adc readback, the following procedure should be completed: 1. read adc_readback_high. this initializes an adc readback. 2. read adc_readback_low. this returns adc_readback[1:0] of the adc sample. 3. read adc_readback_high. this returns adc_readback[7:2] of the adc sample. temperature sensor th e integrated temperature sensor has an operating range between ?40c and +85c. to enable readback of the temperature sensor in phy_off, phy_on, or phy_tx, the following registers must be set: 1. set powerdown_rx (address 0x324) = 0x10 = 0x10. this enables the adc. 2. set powerdown_aux (address 0x325) = 0x02. this enables the temperature sensor. 3. set adc_config_low (address 0x359) = 0x08. this sets the adc input to the temperature sensor. the temperature is determined from the adc readback value using the following formula: temperature (c) = ( adc_readback [7:0] C 42.197)/1.023 + correction value the correction value can be determined by performing a readback at a single known temperature. test dac th e test dac allows the output of the post-demodulator filter to be viewed externally. it takes the 16-bit filter output and converts it to a high frequency, single-bit output using a second- order - converter. the output can be viewed on the gp0 pin. this signal, when filtered appropriately, can be used to ? m onitor the signal at the post-demodulator filter output ? m easure the demodulator output snr ? c onstruct an eye diagram of the received bit stream to measure the received signal quality ? implement analog fm demodulation to enable the test dac, the gpio_configure setting (address 0x3fa) should be set to 0xc9. the test_dac_gain setting (address 0x3fd) should be set to 0x00. the test dac signal at the gp0 pin can be filtered with a 3-stage, low-pass rc filter to reconstruct the demodula ted signal. for more information, see the an-852 application note. transmit test modes there are two transmit test modes that are enabled by setting the var_tx_mode parameter (address 0x00d in packet ram memory), as described in table 42 . var_tx_mode should be set before entering the phy_tx state. table 42. transmit test modes var_tx_mode mode 0 default; no transmit test mode 1 reserved 2 transmit the preamble continuously 3 transmit the carrier continuously 4 to 255 reserved silicon revision readback the product code and silicon revision code can be read from the packet ram memory as described in table 43 . the values of the product code and silicon revision code are valid only on power-up or wake-up from the phy_sleep state because the communications processor overwrites these values on transitioning from the phy_on state. table 43. product code and silicon revision code packet ram location description 0x001 product code, most significant byte = 0x70 0x002 product code, least significant byte = 0x23 0x003 silicon revision code, most significant byte 0x004 silicon revision code least significant byte
adf7023-j rev. 0 | page 74 of 100 applications information application circuit a typical application circuit for the adf7023-j is shown in figure 83 . all external components required for operation of the device, excluding supply decoupling capacitors, are shown. this example circuit uses a combined single-ended pa and lna match. further details on matching topologies and different host processor interfaces are given in the host processor interface section and the pa/lna matching section. host processor interface the interface, when using packet mode, between the adf7023-j and the host processor is shown in figure 81 . in packet mode, all communication between the host processor and the adf7023-j occurs on the spi interface and the irq_gp3 pin. the interface between the adf7023-j and the host processor in sport mode is shown in figure 82 . in sport mode, the transmit and receive data interface consists of the gp0, gp1, and gp2 pins and a separate interrupt is available on gp4, while the spi interface is used for memory access and issuing of commands. adf7023-j cs mosi sclk miso irq_gp3 gp2 gp1 gp0 g p 4 24 v dd 23 22 21 20 19 18 17 25 controller gpio mosi sclk miso irq 09555-158 figure 81. processor interface in packet mode cs mosi sclk miso irq_gp3 gp2 gp1 gp0 g p 4 24 23 22 21 20 19 18 17 25 controller gpio irq mosi sclk miso irq txrxclk txdata rxdata v dd adf7023-j 09555-159 figure 82. processor interface in sport mode adf7023-j cregrf1 pa/lna match rbias cregrf2 rfio_1p rfio_1n rfo2 vddbat2 nc cs mosi sclk miso irq_gp3 gp2 gp1 gp0 g p 4 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 24 23 22 21 20 19 18 17 32 31 30 29 28 27 26 25 vdd controller 32khz xtal (optional) 26mhz xtal gpio mosi sclk miso irq gnd pad creg dig1 dguard xosc26n xosc26p cwakeup creg synth vcoguard creg vco creg dig2 vdd v dd xosc32kp_gp5_atb1 xosc32kn_atb2 vddbat1 adcin_atb3 atb4 adcvref antenna c onnection harmonic filter 09555-039 figure 83. typical adf7023-j application circuit diagram
adf7023-j rev. 0 | page 75 of 100 pa/lna matching the adf7023-j has a differential lna and both a single-ended pa and differential pa. this flexibility allows numerous possibilities in interfacing the adf7023-j to the antenna. combined single-ended pa and lna match the combined single-ended pa and lna match allows the transmit and receive paths to be combined without the use of an external transmit/receive switch. the matching network design is shown in figure 85 . the differential lna match is a five-element discrete balun giving a single-ended input. the single-ended pa output is a three-element match consisting of the choke inductor to the cregrf2 regulated supply and an inductor and capacitor series. the lna and pa paths are combined, and a seventh-order harmonic filter provides attenuation of the transmit harmonics. in a combined match, the off impedances of the pa and lna must be considered. this can lead to a small loss in transmit power and degradation in receiver sensitivity in comparison with a separate single-ended pa and lna match. however, with optimum matching, the typical loss in transmit power is <1 db, and the degradation in sensitivity is <1 db when compared with a separate pa and lna matching topology. separate single-end ed pa/lna match the separate single-ended pa and lna matching configuration is illustrated in figure 84 . the network is the same as the combined matching network shown in figure 85 except that the transmit and receive paths are separate. an external transmit/receive antenna switch can be used to combine the transmit and receive paths to allow connection to an antenna. in designing this matching network, it is not necessary to consider the off impedances of the pa and lna, and, thus, achieving an optimum match is less complex than with the combined single-ended pa and lna match. lna match pa match cregrf2 adf7023-j rfio_1p rfio_1n rfo2 3 4 5 6 rx 09555-161 tx harmonic filter figure 84. separate single -ended pa and lna match combined differential pa/lna match in this matching topology, the single-ended pa is not used. the differential pa and lna match comprises a five-element discrete balun giving a single-ended input/output, as illustrated in figure 86 . the harmonic filter is used to minimize the rf harmonics from the differential pa. match cregrf2 adf7023-j rfio_1p rfio_1n rfo2 3 4 5 6 09555-160 antenna connection harmonic filter figure 85. combined single-ended pa and lna match cregrf2 adf7023-j rfio_1p rfio_1n rfo2 3 4 5 6 09555-162 antenna connection harmonic filter figure 86. combined differential pa and lna match
adf7023-j rev. 0 | page 76 of 100 09555-163 differential pa and lna match single-ended pa match cregrf2 a df7023-j rfio_1p rfio_1n rfo2 3 4 5 6 tx (differentia l pa) and rx harmonic filter tx (single- ended pa) harmonic filter figure 87. matching topology for transmit antenna diversity transmit antenna diversity transmit antenna diversity is possible using the differential pa and single-ended pa. the required matching network is shown in figure 87 . support for external pa and lna control the adf7023-j provides independent control signals for an external pa or lna. if the ext_pa_en bit is set to 1 in the mode_control register (address 0x11a), the external pa control signal is logic high while the adf7023-j is in the phy_tx state and logic low while in any other state. if the ext_lna_en bit is set to 1 in the mode_control register (address 0x11a), the external lna control signal is logic high while the adf7023-j is in the phy_rx state and logic low while in any other state. the external pa and lna control signals can be configured using the ext_pa_lna_config setting (address 0x11b) as described in table 44 . table 44. configuration of the external pa and lna control signals ext_pa_lna_config configuration 0 external pa signal on adcin_atb3 and external lna signal on atb4 (1.8 v logic outputs) 1 external pa signal on xosc32kp_gp5_atb1 and external lna signal on xosc32kn_atb2 (v dd logic outputs)
adf7023-j rev. 0 | page 77 of 100 command reference table 45. radio controller commands command code description cmd_sync 0xa2 synchronizes the communications processor to the host processor after reset. cmd_phy_off 0xb0 performs a transition of the device into the phy_off state. cmd_phy_on 0xb1 performs a transition of the device into the phy_on state. cmd_phy_rx 0xb2 performs a transition of the device into the phy_rx state. cmd_phy_tx 0xb5 performs a transition of the device into the phy_tx state. cmd_phy_sleep 0xba performs a transition of the device into the phy_sleep state. cmd_config_dev 0xbb configures the radio parameters based on the bbram values. cmd_get_rssi 0xbc performs an rssi measurement. cmd_bb_cal 0xbe performs a calibration of the if filter. cmd_hw_reset 0xc8 performs a full hardware reset. the device enters the phy_sleep state. cmd_ram_load_init 0xbf prepares the program ram for a firmware module download. cmd_ram_load_done 0xc7 performs a reset of the communications processor after download of a firmware module to program ram. cmd_ir_cal 1 0xbd initiates an image rejection calibration routine. cmd_aes_encrypt 2 0xd0 performs an aes encryption on the tran smit payload data stored in packet ram. cmd_aes_decrypt 2 0xd2 performs an aes decryption on the rece ived payload data stored in packet ram. cmd_aes_decrypt_init 2 0xd1 initializes the internal variables required for aes decryption. cmd_rs_encode_init 3 0xd1 initializes the internal variables required for the reed solomon encoding. cmd_rs_encode 3 0xd0 calculates and appends the reed-solomon check bytes to the transmit payload data stored in packet ram. cmd_rs_decode 3 0xd2 performs a reed-solomon error correction on the received payload data stored in packet ram. 1 the image rejection calibration firmware module must be loaded to program ram for this command to be functional. 2 the aes firmware module must be loaded to program ram for this command to be functional. 3 the reed-solomon coding firmware module must be loaded to program ram for this command to be functional. table 46. spi commands command code description spi_mem_wr 00011xxxb = 0x18 (packet ram), 0x19 (bbram), 0x1b (mcr), 0x1e (program ram) writes data to bbram, mcr, or packet ram memory sequentially. an 11-bit address is used to identify memory locations. the most significant three bits of the address are incorporated into the command (xxxb). this command is followed by the remaining eight bits of the address, whic h are subsequently followed by the data bytes to be written. spi_mem_rd 00111xxxb = 0x38 (packet ram), 0x39 (bbram), 0x3b (mcr) reads data from bbram, mcr, or packet ram memory sequentially. an 11-bit address is used to identify memory locations. the most significant three bits of the address are incorporated into the command (xxxb). this command is followed by the remaining eight bits of the address, which are subsequently followed by the appropriate number of spi_nop commands. spi_memr_wr 00001xxxb = 0x08 (packet ram), 0x09 (bbram), 0x0b (mcr) writes data to bbram, mcr, or packet ram memory nonsequentially. spi_memr_rd 00101xxxb = 0x28 (packet ram), 0x29 (bbram), 0x2b (mcr) reads data from bbram, mcr, or pack et ram memory nonsequentially. spi_nop 0xff no operation. use for dummy writes when polling the status word; used also as dummy data when performing a memory read.
adf7023-j rev. 0 | page 78 of 100 register maps table 47. battery backup memory (bbram) address (hex) register retained in phy_sleep r/w group 0x100 interrupt_mask_0 yes r/w mac 0x101 interrupt_mask_1 yes r/w mac 0x102 number_of_wakeups_0 yes r/w mac 0x103 number_of_wakeups_1 yes r/w mac 0x104 number_of_wakeups_irq_threshold_0 yes r/w mac 0x105 number_of_wakeups_irq_threshold_1 yes r/w mac 0x106 rx_dwell_time yes r/w mac 0x107 parmtime_divider yes r/w mac 0x108 swm_rssi_thresh yes r/w phy 0x109 channel_freq_0 yes r/w phy 0x10a channel_freq_1 yes r/w phy 0x10b channel_freq_2 yes r/w phy 0x10c radio_cfg_0 yes r/w phy 0x10d radio_cfg_1 yes r/w phy 0x10e radio_cfg_2 yes r/w phy 0x10f radio_cfg_3 yes r/w phy 0x110 radio_cfg_4 yes r/w phy 0x111 radio_cfg_5 yes r/w phy 0x112 radio_cfg_6 yes r/w phy 0x113 radio_cfg_7 yes r/w phy 0x114 radio_cfg_8 yes r/w phy 0x115 radio_cfg_9 yes r/w phy 0x116 radio_cfg_10 yes r/w phy 0x117 radio_cfg_11 yes r/w phy 0x118 image_reject_cal_phase yes r/w phy 0x119 image_reject_cal_amplitude yes r/w phy 0x11a mode_control yes r/w phy 0x11b preamble_match yes r/w packet 0x11c symbol_mode yes r/w packet 0x11d preamble_len yes r/w packet 0x11e crc_poly_0 yes r/w packet 0x11f crc_poly_1 yes r/w packet 0x120 sync_control yes r/w packet 0x121 sync_byte_0 yes r/w packet 0x122 sync_byte_1 yes r/w packet 0x123 sync_byte_2 yes r/w packet 0x124 tx_base_adr yes r/w packet 0x125 rx_base_adr yes r/w packet 0x126 packet_length_control yes r/w packet 0x127 packet_length_max yes r/w packet 0x128 static_reg_fix yes r/w phy 0x129 address_match_offset yes r/w packet 0x12a address_length yes r/w packet 0x12b to 0x13d address matching yes r/w packet 0x13e rx_synth_lock_time yes r/w phy 0x13f tx_synth_lock_time yes r/w phy
adf7023-j rev. 0 | page 79 of 100 table 48. modem configuration memory (mcr) address (hex) register retained in phy_sleep r/w 0x307 pa_level_mcr no r/w 0x30c wuc_config_high no w 0x30d wuc_config_low no w 0x30e wuc_value_high no w 0x30f wuc_value_low no w 0x310 wuc_flag_reset no r/w 0x311 wuc_status no r 0x312 rssi_readback no r 0x315 max_afc_range no r/w 0x319 image_reject_cal_config no r/w 0x322 chip_shutdown no r/w 0x324 powerdown_rx no r/w 0x325 powerdown_aux no r/w 0x327 adc_readback_high no r 0x328 adc_readback_low no r 0x32d battery_monitor_threshold_voltage no r/w 0x32e ext_uc_clk_divide no r/w 0x32f agc_clk_divide no r/w 0x336 interrupt_source_0 no r/w 0x337 interrupt_source_1 no r/w 0x338 calibration_control no r/w 0x339 calibration_status no r 0x345 rxbb_cal_calwrd_readback no r 0x346 rxbb_cal_calwrd_overwrite no rw 0x359 adc_config_low no r/w 0x35a adc_config_high no r/w 0x35b reserved no r/w 0x35c agc_config no r/w 0x35d agc_mode no r/w 0x35e agc_low_threshold no r/w 0x35f agc_high_threshold no r/w 0x360 agc_gain_status no r 0x372 frequency_error_readback no r 0x3cb vco_band_ovrw_val no r/w 0x3cc vco_ampl_ovrw_val no r/w 0x3cd vco_ovrw_en no r/w 0x3d0 vco_cal_cfg no r/w 0x3d2 osc_config no r/w 0x3da vco_band_readback no r 0x3db vco_ampl_readback no r 0x3f8 analog_test_bus no r/w 0x3f9 rssi_tstmux_sel no r/w 0x3fa gpio_configure no r/w 0x3fd test_dac_gain no r/w
adf7023-j rev. 0 | page 80 of 100 table 49. packet ram memory address register r/w 0x000 var_command r/w 0x001 1 product code, most significant byte = 0x70 r 0x002 1 product code, least significant byte = 0x23 r 0x003 1 silicon revision code, most significant byte r 0x004 1 silicon revision code, least significant byte r 0x005 to 0x00b reserved r 0x00d var_tx_mode r/w 0x00e to 0x00f reserved r 0x010 to 0x018 custom pll loop filter look-up table r/w 1 only valid on power-up or wake-up from the phy_sleep state because the communications processor overwrites these values on exi t from the phy_on state. bbram register description table 50. 0x100: interrupt_mask_0 bit name r/w description [7] interrupt_num_wakeups r/w interrupt when the number of wuc wake-ups (number_of_wakeups[15:0]) has reached the threshold (number_of _wakeups_irq_threshold[15:0]) 1: interrupt enabled; 0: interrupt disabled [6] interrupt_swm_rssi_det r/w interrupt when the measured rssi during smart wake mode has exceeded the rssi threshold value (swm_rssi_thresh, address 0x108) 1: interrupt enabled; 0: interrupt disabled [5] interrupt_aes_done r/w interrupt when an aes encryption or decryption command is complete; available only when the aes firmware module has been loaded to the adf7023-j program ram 1: interrupt enabled; 0: interrupt disabled [4] interrupt_tx_eof r/w interrupt when a packet has finished transmitting 1: interrupt enabled; 0: interrupt disabled [3] interrupt_address_match r/w interrupt when a received packet has a valid address match 1: interrupt enabled; 0: interrupt disabled [2] interrupt_crc_correct r/w interrupt when a received packet has the correct crc 1: interrupt enabled; 0: interrupt disabled [1] interrupt_sync_detect r/w interrupt when a qualified sync word has been detected in the received packet 1: interrupt enabled; 0: interrupt disabled [0] interrupt_premable_detect r/w interrupt when a qualifie d preamble has been detected in the received packet 1: interrupt enabled; 0: interrupt disabled table 51. 0x101: interrupt_mask_1 bit name r/w description [7] battery_alarm r/w interrupt when the battery voltage has dropped below the threshold value (battery_monitor_threshold_voltage, address 0x32d) 1: interrupt enabled; 0: interrupt disabled [6] cmd_ready r/w interrupt when the communications processor is ready to load a new command; mirrors the cmd_ready bit of the status word 1: interrupt enabled; 0: interrupt disabled [5] reserved r/w [4] wuc_timeout r/w interrupt when the wuc has timed out 1: interrupt enabled; 0: interrupt disabled [3] reserved r/w [2] reserved r/w [1] spi_ready r/w interrupt when the spi is ready for access 1: interrupt enabled; 0: interrupt disabled [0] cmd_finished r/w interrupt when the communications processor has finished performing a command 1: interrupt enabled; 0: interrupt disabled
adf7023-j rev. 0 | page 81 of 100 table 52. 0x102: number_of_wakeups_0 bit name r/w description [7:0] number_of_wakeups[7:0] r/w bits[7:0] of [15:0] of an internal 16 -bit count of the number of wake-ups (wuc timeouts) the device has gone through. it can be initialized to 0x0000. see table 53 . table 53. 0x103: number_of_wakeups_1 bit name r/w description [7:0] number_of_wakeups[15:8] r/w bits[15:8] of [15:0] of an internal 16-bit count of the number of wuc wake-ups the device has gone through. it can be initialized to 0x0000. see table 52 . table 54. 0x104: number_of_wakeups_irq_threshold_0 bit name r/w description [7:0] number_of_wakeups_irq_threshold[7:0] r/w bits[7:0] of [15:0] (see table 55 ). the threshold for the number of wake-ups (wuc timeouts). it is a 16-bit count threshold that is compared against the number_of_wakeups bits. when this threshold is exceeded, the device wakes up in the phy_off state and optionally generates interrupt_num_wakeups. table 55. 0x105: number_of_wakeups_irq_threshold_1 bit name r/w description [7:0] number_of_wakeups_irq_threshold[ 15:8] r/w bits[15:8] of [15:0] (see table 54 ). table 56. 0x106: rx_dwell_time bit name r/w description [7:0] rx_dwell_time r/w when the wuc is used and swm is enabled, the radio powers up and enables the receiver on the channel defined in the bbram and listens for this period of time. if no preamble pa ttern is detected in this period, the device goes back to sleep. receive dwell time (s) = rx_dwell_time ivider parmtime_d 128 mhz6.5 table 57. 0x107: parmtime_divider bit name r/w description [7:0] parmtime_divider r/w units of time used to define the rx_dwell_time time period. timer tick rate = mhz6.5 128 ivider parmtime_d a value of 0x33 gives a clock of 995.7 hz or a period of 1.004 ms. table 58. 0x108: swm_rssi_thresh bit name r/w description [7:0] swm_rssi_thresh r/w this sets the rssi threshold when in smart wake mode with rssi detection enabled. threshold (dbm) = swm_rssi_thresh ? 107 table 59. 0x109: channel_freq_0 bit name r/w description [7:0] channel_freq[7:0] r/w the rf channel frequency in hertz is set according to 16 2 ) ( 0]:eq[23 channel_fr pfd f(hz) frequency = where f pfd is the pfd frequency and is equal to 26 mhz.
adf7023-j rev. 0 | page 82 of 100 table 60. 0x10a: channel_freq_1 bit name r/w description [7:0] channel_freq[15:8] r/w see the channel_freq_0 description in table 59 . table 61. 0x10b: channel_freq_2 bit name r/w description [7:0] channel_freq[23:16] r/w see the channel_freq_0 description in table 59 . table 62. 0x10c: radio_cfg_0 bit name r/w description [7:0] data_rate[7:0] r/w the data rate in bps is set according to data rate (bps) = data_rate[11:0] 100. table 63. 0x10d: radio_cfg_1 bit name r/w description [7:4] freq_deviation[11:8] r/w see the freq _deviation description in radio_cfg_2 (see table 64 ). [3:0] data_rate[11:8] r/w see the data_rate description in radio_cfg_0 (see table 62 ). table 64. 0x10e: radio_cfg_2 bit name r/w description [7:0] freq_deviation[7:0] r/w the binary level 2fsk/gfsk/msk/gmsk frequency deviation in hertz (defined as the frequency difference between ca rrier frequency and 1/0 tones) is set according to frequency deviation (hz) = freq_deviation[11:0] 100. table 65. 0x10f: radio_cfg_3 bit name r/w description [7:0] discrim_bw[7:0] r/w the discrim_bw value sets the bandwidth of the correlator demodulator. see the 2fsk/gfsk/msk/gmsk demodulation section for the steps required to set the discrim_bw value. table 66. 0x110: radio_cfg_4 bit name r/w description [7:0] post_demod_bw[7:0] r/w for optimum performance, the post-demod ulator filter bandwidth should be set close to 0.75 times the data rate. the actual bandwidth of the post- demodulator filter is given by post-demodulator filter bandwidth (khz) = post_demod_bw 2. the range of post_demod_bw is 1 to 255. table 67. 0x111: radio_cfg_5 bit name r/w description [7:0] reserved r/w set to zero. table 68. 0x112: radio_cfg_6 bit name r/w description [7:2] synth_lut_config_0 r/w if synth_lut_control (address 0x113, table 69 ) = 0 or 2, set synth_lut_config_0 = 0. if synth_lut_control = 1 or 3, this setting allows the receiver pll loop bandwidth to be changed to optimize the receiver local oscillator phase noise. [1:0] discrim_phase[1:0] r/w the discrim_phase value sets the phase of the correlator demodulator. see the 2fsk/gfsk/msk/gmsk demodulation section for the steps required to set the discrim_phase value.
adf7023-j rev. 0 | page 83 of 100 table 69. 0x113: radio_cfg_7 bit name r/w description [7:6] agc_lock_mode r/w set to: 0: free running 1: manual 2: hold 3: lock after preamble/sync word (onl y locks on a sync word if preamble_ match = 0) [5:4] synth_lut_control r/w by default, the synthesizer loop band width is automatically selected from lookup tables (lut) in rom memory. a narrow bandwidth is selected in receive to ensure optimum interference rejection, whereas in transmit, the bandwidth is selected based on the data rate and modulation settings. for the majority of applications, thes e automatically selected pll loop bandwidths are optimum. however, in some applications, it may be necessary to use custom transmit or receive bandwidths, in which case, various options exist, as follows. synth_lut_control description 0 use predefined transmit and receive luts. the luts are automatically selected from rom memory on transitioning into the phy_tx or phy_rx state. 1 use custom receive lut based on synth_ lut_config_0 and synth_lut_config_1. in transmit, the predefined lut in rom is used. 2 use a custom transmit lut. the custom transmit lut must be written to the 0x10 to 0x18 packet ram locations. in receive, the predefined lut in rom is used. 3 use a custom receive lut based on synth_ lut_config_0 and synth_lut_config_1, and use a custom transmit lut. the custom transmit lut must be written to the 0x10 to 0x18 packet ram locations. because packet ram memory is lost in the phy_sleep state, the custom lut for transmit must be reloaded to packet ram after waking from the phy_sleep state. [3:0] synth_lut_config_1 r/w if synth_lut_control = 0 or 2, set synth_lut_config_0 to 0. if synth_lut_control = 1 or 3, this se tting allows the receiver pll loop bandwidth to be changed to optimize the receiver local oscillator phase noise. table 70. 0x114: radio_cfg_8 bit name r/w description [7] pa_single_diff_sel r/w pa_single_diff_sel pa 0 single-ended pa enabled 1 differential pa enabled [6:3] pa_level r/w sets the pa output power. a value of zero sets the minimum rf output power, and a value of 15 sets the maximum pa output power. the pa level can also be set with fi ner resolution using the pa_level_mcr setting (address 0x307). the pa_level setting is related to the pa_level_mcr setting by pa_level_mcr = 4 pa_level + 3. pa_level pa level (pa_level_mcr) 0 setting 3 1 setting 7 2 setting 11 15 setting 63
adf7023-j rev. 0 | page 84 of 100 bit name r/w description [2:0] pa_ramp r/w sets the pa ramp rate. the pa ramps at the programmed rate until it reaches the level indicated by the pa_level_mcr (address 0x307) setting. the ramp rate is dependent on the programmed data rate. pa_ramp ramp rate 0 reserved 1 256 codes per data bit 2 128 codes per data bit 3 64 codes per data bit 4 32 codes per data bit 5 16 codes per data bit 6 eight codes per data bit to ensure the correct pa ramp-up and ramp-down timing, the pa ramp rate has a minimum value based on the data rate and the pa_level or pa_level_mc r settings. this minimum value is described by 0]:11 data_rate[ 2500< 0]:cr[5 pa_level_m /bit) rate(codes ramp where pa_level_mcr is related to the pa_level setting by pa_level_mcr = 4 pa_level + 3. table 71. 0x115: radio_cfg_9 bit name r/w description [7:6] ifbw r/w sets the receiver if filter bandwidth. note that se tting an if filter bandwidth of 300 khz automatically changes the receiver if frequency from 200 khz to 300 khz. ifbw if bandwidth (khz) 0 100 1 150 2 200 3 300 [5:3] mod_scheme r/w sets the transmitter modulation scheme. mod_scheme modulation scheme 0 two-level 2fsk/msk 1 two-level gfsk/gsmk 2 reserved 3 carrier only 4 to 7 reserved [2:0] demod_scheme r/w sets the receiver demodulation scheme. demod_scheme demodulation scheme 0 2fsk/gfsk/msk/gmsk 1 reserved 2 reserved 3 to 7 reserved table 72. 0x116: radio_cfg_10 bit name r/w description [7:5] reserved r/w set to 0. [4] afc_polarity r/w set to 0. [3:2] afc_scheme r/w set to 2. [1:0] afc_lock_mode r/w sets the afc mode. afc_lock_mode mode 0 free running: afc is free running. 1 disabled: afc is disabled. 2 hold afc: afc is paused. 3 lock: afc locks after the preamble or sync word (only locks on a sync word if preamble_match = 0).
adf7023-j rev. 0 | page 85 of 100 table 73. 0x117: radio_cfg_11 bit name r/w description [7:4] afc_kp r/w sets the afc pi controller proportion al gain in 2fsk/gfsk/msk/gmsk; the recommended value is 0x3. afc_kp proportional gain 0 2 0 1 2 1 2 2 2 15 2 15 [3:0] afc_ki r/w sets the afc pi controller integral gain in 2fsk/gfsk/msk/gmsk; the recommended value is 0x7. afc_ki integral gain 0 2 0 1 2 1 2 2 2 15 2 15 table 74. 0x118: image_reject_cal_phase bit name r/w description [7] reserved r/w set to 0 [6:0] image_reject_cal_phase r/w sets the i/q phase adjustment table 75. 0x119: image_reject_cal_amplitude bit name r/w description [7] reserved r/w set to 0 [6:0] image_reject_cal_amplitude r/w sets the i/q amplitude adjustment table 76. 0x11a: mode_control bit name r/w description [7] swm_en r/w 1: smart wake mode enabled. 0: smart wake mode disabled. [6] bb_cal r/w 1: if filter calibration enabled. 0: if filter calibration disabled. if filter calibration is automatically perf ormed on the transition from the phy_off state to the phy_on state if this bit is set. [5] swm_rssi_qual r/w 1: rssi qualify in low power mode enabled. 0: rssi qualify in low power mode disabled. [4] tx_to_rx_auto_turnaround r/w if tx_to_rx_auto_turnaround = 1, the device automatically transitions to the phy_rx state at the end of a packet transmission, on the same rf channel frequency. if tx_to_rx_auto_turnaround = 0, this operation is disabled. tx_to_rx_auto_turnaround is only available in packet mode. [3] rx_to_tx_auto_turnaround r/w if rx_to_tx_auto_turnaround = 1, the device automatically transitions to the phy_tx state at the end of a valid packet reception, on the same rf channel frequency. if rx_to_tx_auto_turnaround = 0, this operation is disabled. rx_to_tx_auto_turnaround is only available in packet mode. [2] custom_trx_synth_lock_time_en r/w 1: use the custom synthesizer lock time defined in register 0x13e and register 0x13f. 0: default synthesizer lock time. [1] ext_lna_en r/w 1: external lna enable signal on atb4 is enabled. the signal is logic high while the adf7023-j is in the phy_rx state and logic low while in any other nonsleep state. 0: external lna enable signal on atb4 is disabled. [0] ext_pa_en r/w 1: external pa enable signal on atb3 is enabled. the signal is logic high while the adf7023-j is in the phy_tx state and logic low while in any other nonsleep state. 0: external pa enable signal on adcin_atb3 is disabled.
adf7023-j rev. 0 | page 86 of 100 table 77. 0x11b: preamble_match bit name r/w description [7] ext_pa_lna_config r/w ext_pa_lna_config description 0 external pa signal on adcin_atb3 and external lna signal on atb4 (1.8 v logic outputs) 1 external pa signal on xosc32kp_gp5_atb1 and external lna signal on xosc32kn_atb2 (v dd logic outputs) [6:4] reserved r/w set to 0 [3:0] preamble_match r/w preamble_match description 15 to 13 reserved 12 0 errors allowed 11 one erroneous bit pair allowed in 12 bit-pairs 10 two erroneous bit pairs allowed in 12 bit-pairs 9 three erroneous bit pairs allowed in 12 bit-pairs 8 four erroneous bit pairs allowed in 12 bit-pairs 7 to 1 not recommended 0 preamble detection disabled table 78. 0x11c: symbol_mode bit name r/w description [7] reserved r/w set to 0 [6] manchester_enc r/w 1: manchester encoding and decoding enabled 0: manchester encoding and decoding disabled [5] prog_crc_en r/w 1: programmable crc enabled 0: programmable crc disabled [4] eight_ten_enc r/w 1: 8b/10b encoding and decoding enabled 0: 8b/10b encoding and decoding disabled [3] data_whitening r/w 1: data whitening and dewhitening enabled 0: data whitening and dewhitening disabled [2:0] symbol_length r/w symbol_length description 0 8-bit (recommended except when 8b/10b is being used) 1 10-bit (for 8b/10b encoding) 2 to 7 reserved table 79. 0x11d: preamble_len bit name r/w description [7:0] preamble_len r/w length of preamble in bytes. example: a value of decimal 3 results in a preamble of 24 bits. table 80. 0x11e: crc_poly_0 bit name r/w description [7:0] crc_poly[7:0] r/w lower byte of crc_poly[15:0], which sets the crc polynomial. see table 81 . table 81. 0x11f: crc_poly_1 bit name r/w description [7:0] crc_poly[15:8] r/w upper byte of crc_poly[15:0], which sets the crc polynomial. see the packet mode section for more details on how to configure a crc polynomial.
adf7023-j rev. 0 | page 87 of 100 table 82. 0x120: sync_control bit name r/w description [7:6] sync_error_tol r/w sets the sync word error tolerance in bits. sync_error_tol bit error tolerance 0 0 bit errors allowed. 1 one bit error allowed. 2 two bit errors allowed. 3 three bit errors allowed. [5] reserved r/w set to 0. [4:0] sync_word_length r/w sets the sync word length in bits; 24 bits is the maximum. note that the sync word matching length can be any va lue up to 24 bits, but the transmitted sync word pattern is a multiple of eight bits. therefore, for nonbyte-length sync words, the transmitted sync pattern should be filled out with the preamble pattern. sync_word_length length in bits 0 0 1 1 24 24 table 83. 0x121: sync_byte_0 bit name r/w description [7:0] sync_byte[7:0] r/w lower byte of the sync word pattern. the sync word pattern is transmitted most significant bit first starting with sync_byte_0. for nonbyte-length sync words, the remainder of the least significant byte should be stuffed with the preamble. if sync_word_length length is >16 bits, sync_byte_0, sync_byte_1, and sync_byte_2 are all transmitted for a total of 24 bits. if sync_word_length is between 8 and 15, sync_byte_1 and sync_byte_2 are transmitted. if sync_word_length is between 1 and 7, sync_byte_2 is transmitted for a total of eight bits. if the sync_word_length is 0, no sync bytes are transmitted. table 84. 0x122: sync_byte_1 bit name r/w description [7:0] sync_byte[15:8] r/w middle byte of the sync word pattern table 85. 0x123: sync_byte_2 bit name r/w description [7:0] sync_byte[23:16] r/w upper byte of the sync word pattern table 86. 0x124: tx_base_adr bit name r/w description [7:0] tx_base_adr r/w address in packet ram of the transmit packet. this address indicates to the communications processor the location of the first byte of the transmit packet. table 87. 0x125: rx_base_adr bit name r/w description [7:0] rx_base_adr r/w address in packet ram of the receive packet. the communications processor writes any qualified received packet to packet ram, starting at this memory location.
adf7023-j rev. 0 | page 88 of 100 table 88. 0x126: packet_length_control bit name r/w description [7] data_byte r/w over-the-air arrangement of each transmitted packet ram byte. a byte is transmitted either msb or lsb first. the same setting should be used on the tx and rx sides of the link. 1: data byte msb first. 0: data byte lsb first. [6] packet_len r/w 1: fixed packet length mode. fixed pack et length in tx and rx modes, given by packet_length_max. 0: variable packet length mode. in rx mode, packet length is given by the first byte in packet ram. in tx mode, the packet length is given by packet_length_max. [5] crc_en r/w 1: append crc in transmit mode. check crc in receive mode. 0: no crc addition in transmit mode. no crc check in receive mode. [4:3] data_mode r/w sets the adf7023-j to packet mode or sport mode for transmit and receive data. data_mode description 0 packet mode enabled. 1 sport mode enabled. gp4 interrupt enabled on preamble detection. rx data enabled on preamble detection. 2 sport mode enabled. gp4 interrupt enabled on sync word detection. rx data enabled on preamble detection. 3 unused. [2:0] length_offset r/w offset value in bytes that is added to the received packet length field value (in variable length packet mode) so that the communications processor knows the correct number of bytes to read. the communications processor calculates the actual received payload length as rx payload length = length + length_offset C 4, where length is th e length field (the first byte in the received payload). table 89. 0x127: packet_length_max bit name r/w description [7:0] packet_length_max r/w if variable packet length mode is used (packet_length_control = 0), packet_length_max sets the maximum receive packet length in bytes. if fixed packet length mode is used (packet_length_control = 1), packet_length_max sets the length of the fixed transmit and receive packet in bytes. note that the packet length is defined as the number of bytes from the end of the sync word to the start of the crc. it also does not include the length_offset value.
adf7023-j rev. 0 | page 89 of 100 table 90. 0x128: static_reg_fix bit name r/w description [7:0] static_reg_fix r/w th e adf7023-j has the ability to implement automatic static register fixes from bbram memory to mcr memory. this feature allows a maximum of nine mcr registers to be programmed via bbram memory. this feature is useful if mcr registers must be configured for optimum receiver performance in low power mode. the static_reg_fix value is an address pointer to any bbram memory address between 0x12a and 0x13d. for example, to point to bbram address 0x12b, set static_reg_fix = 0x2b. ? i f static_reg_fix = 0x00, then static register fixes are disabled. ? if static_reg_fix is nonzero, th e communications processor looks for the mcr address and corresponding data at the bbram address beginning at static_reg_fix. example: write 0x46 to mcr register 0x35e and write 0x78 to mcr register 0x35f. set static_reg_fix = 0x2b. bbram register data description 0x128 (static_reg_fix) 0x2b pointer to bbram address 0x12b 0x12b 0x5e mcr address 1 0x12c 0x46 data to write to mcr address 1 0x12d 0x5f mcr address 2 0x12e 0x78 data to write to mcr address 2 0x12f 0x00 ends static mcr register fixes table 91. 0x129: address_match_offset bit name r/w description [7:0] address_match_offset r/w location of firs t byte of address information in packet ram table 92. 0x12a: address_length bit name r/w description [7:0] address_length r/w number of bytes in the first address field (n adr_1 ). set to zero if address matching is not being used. table 93. 0x12b to 0x13d: address matching address bit r/w description 0x12b [7:0] r/w address 1 match byte 0. 0x12c [7:0] r/w address 1 mask byte 0. 0x12d [7:0] r/w address 1 match byte 1. 0x12e [7:0] r/w address 1 mask byte 1. [7:0] r/w address 1 match byte n adr_1 . [7:0] r/w address 1 mask byte n adr_1 . [7:0] r/w 0x00 to end or number of bytes in the second address field (n adr_2 ). table 94. 0x13e: rx_synth_lock_time bit name r/w description [7:0] rx_synth_lock_time r/w allows the use of a custom synthesizer lock time counter in receive mode in conjunction with the custom_trx_synth_lock_time_en setting in the mode_control register. applies after vco calibration is complete. each bit equates to a 2 s increment. table 95. 0x13f: tx_synth_lock_time bit name r/w description [7:0] tx_synth_lock_time r/w allows the use of a custom synthesizer lo ck time counter in transmit mode in conjunction with the custom_trx_synth_lock_time_en setting in the mode_control register. applies after vco calibration is complete. each bit equates to a 2 s increment.
adf7023-j rev. 0 | page 90 of 100 mcr register description the mcr register settings are not retained when the device enters the phy_sleep state. table 96. 0x307: pa_level_mcr bit name r/w reset description [5:0] pa_level_mcr r/w 0 power amplifier level. if pa ramp is enabled, the pa ramps to this target level. the pa level can be set in the 0 to 63 range. the pa level (with less resolution) can also be set via the bbram; therefore, the mcr setting should be used only if more resolution is required. table 97. 0x30c: wuc_config_high bit name r/w reset description [7] reserved w 0 set to 0 [6] wuc_bgap w 0 set to 0 [5] wuc_ldo_synth w 0 set to 0 [4] wuc_ldo_dig w 0 set to 0 [3] wuc_xto26m_en w 0 set to 0 [2:0] wuc_prescaler w 0 wuc_prescaler 32.768 khz divider tick period 0 1 30.52 s 1 4 122.1 s 2 8 244.1 s 3 16 488.3 s 4 128 3.91 ms 5 1034 31.25 ms 6 81 2 250 ms 7 65,536 2000 ms register wuc_config_low should never be written to without updating register wuc_config_high first. table 98. 0x30d: wuc_config_low bit name r/w reset description [7] reserved w 0 set to 0 [6] wuc_rcosc_en w 0 1: enable rcosc32k 0: disable rcosc32k [5] wuc_xosc32k_en w 0 1: enable xosc32k 0: disable xosc32k [4] wuc_clksel w 0 select the wuc timer clock source 1: rc 32.768 khz oscillator 0: external crystal oscillator [3] wuc_bbram_en w 0 1: enable power to the bbram during the phy_sleep state 0: disable power to the bbram during the phy_sleep state [2:1] reserved w 0 set to 0 [0] wuc_arm w 0 1: enable wake-up on a wuc timeout event 0: disable wake-up on a wuc timeout event updates to register wuc_value_high become effective only after register wuc_value_low is written to. table 99. 0x30e: wuc_value_high bit name r/w reset description [7:0] wuc_timer_value[15:8] w 0 wuc timer reload value, bits[15:8] of [15:0]. a wake-up event is triggered when the wuc unit is enabled and th e timer has counted down to 0. the timer is clocked with the prescaler outp ut rate. an update to this register becomes effective only after wuc_value_low is written. see table 100 .
adf7023-j rev. 0 | page 91 of 100 register wuc_value_low should never be written to without updating register wuc_value_high first. table 100. 0x30f: wuc_value_low bit name r/w reset description [7:0] wuc_timer_value[7:0] w 0 wuc timer reload value, bits[7:0] of [15:0]. a wake-up event is triggered when the wuc unit is enabled and th e timer has counted down to 0. the timer is clocked with the prescaler output rate. see table 101 . table 101. 0x310: wuc_flag_reset bit name r/w reset description [1] wuc_rcosc_cal_en r/w 0 1: enable 0: disable rcosc32k calibration [0] wuc_flag_reset r/w 1: reset the wuc_tmr_prim_toflag and wuc_porflag bits (address 0x311, see table 102 ) 0: normal operation table 102. 0x311: wuc_status bit name r/w reset description [7] reserved r 0 reserved [6] wuc_rcosc_cal_error r 0 1: rcosc32k calibration exited with error 0: without error (only valid if wuc_rcosc_cal_en = 1) [5] wuc_rcosc_cal_ready r 0 1: rcosc32k calibration finished 0: in progress (only valid if wuc_rcosc_cal_en = 1) [4] xosc32k_rdy r 0 1: xosc32k oscillator has settled 0: not settled (only valid if wuc_xosc32k_en = 1) [3] xosc32k_out r 0 output signal of the xosc32k oscillator (instantaneous) [2] wuc_porflag r 0 1: chip cold start event has been registered 0: not registered [1] wuc_tmr_prim_toflag r 0 1: wuc ti meout event has been registered 0: not registered (the output of a latch triggered by a timeout event) [0] wuc_tmr_prim_toevent r 0 1: wuc timeout event is present 0: not present (this bit is set when the counter reaches 0; it is not latched) table 103. 0x312: rssi_readback bit name r/w reset description [7:0] rssi_readback r 0 receive input power. after reception of a packet, the rssi_readback value is valid. rssi (dbm) = rssi_readback C 107. table 104. 0x315: max_afc_range bit name r/w reset description [7:0] max_afc_range r/w 50 limits the afc pull-in range. automatically set by the communications processor on transitioning into the phy_rx state. the range is set equal to half the if bandwidth. example: if bandwidth = 200 khz, afc pull-in range = 100 khz (max_afc_range = 100).
adf7023-j rev. 0 | page 92 of 100 table 105. 0x319: image_reject_cal_config bit name r/w reset description [7:6] reserved r/w 0 [5] image_reject_cal_ovwrt_en r/w 0 overwrite control for image reject calibration results. [4:3] image_reject_frequency r/w 0 set the fundamental frequency of the ir calibration signal source. a harmonic of this frequency can be used as an in ternal rf signal source for the image rejection calibration. 0: ir calibration source disabled in xtal divider 1: ir calibration source fundamental frequency = xtal/4 2: ir calibration source fundamental frequency = xtal/8 3: ir calibration source fundamental frequency = xtal/16 [2:0] image_reject_power r/w 0 set power level of ir calibration source. 0: ir calibration sour ce disabled at mixer input 1: power level = min 2: power level = min 3: power level = min 2 4: power level = min 2 5: power level = min 3 6: power level = min 3 7: power level = min 4 table 106. 0x322: chip_shutdown bit name r/w reset description [7:1] reserved r/w 0 [0] chip_shtdn_req r/w 0 wuc chip-state control flag 0: remain in active state 1: invoke chip shutdown. cs must also be high to initiate a shutdown table 107. 0x324: powerdown_rx bit name r/w reset description [7:5] reserved r/w 0 [4] adc_pd_n r/w 0 1: lna enabled 0: lna disabled [3] rssi_pd_n r/w 0 1: rssi enabled 0: rssi disabled [2] rxbbfilt_pd_n r/w 0 1: if filter enabled 0: if filter disabled [1] rxmixer_pd_n r/w 0 1: mixer enabled 0: mixer disabled [0] lna_pd_n r/w 0 1: lna enabled 0: lna disabled table 108. 0x325: powerdown_aux bit name r/w reset description [7:2] reserved r/w 0 [1] tempmon_pd_en r/w 0 1: enable 0: disable temperature monitor [0] battmon_pd_en r/w 0 1: enable 0: disable battery monitor table 109. 0x327: adc_readback_high bit name r/w reset description [7:6] reserved r 0 [5:0] adc_readback[7:2] r 0 adc readback of msbs
adf7023-j rev. 0 | page 93 of 100 table 110. 0x328: adc_readback_low bit name r/w reset description [7:6] adc_readback[1:0] r 0 adc readback of lsbs [5:0] reserved r 0 table 111. 0x32d: battery_monitor_threshold_voltage bit name r/w reset description [7:5] reserved r/w 0 [4:0] battmon_voltage r/w 0 the battery monitor threshold voltage sets the alarm level for the battery monitor. the alarm is raised by the interrupt. battery monitor trip voltage, v trip = 1.7 v + 62 mv battmon_voltage. table 112. 0x32e: ext_uc_clk_divide bit name r/w reset description [7:4] reserved r/w 0 [3:0] ext_uc_clk_divide r/w 4 optional output clock frequency on xosc32kp_gp5_atb1. output frequency = xtal/ext_uc_clk_divide. to disable, set ext_uc_clk_divide = 0. table 113. 0x32f: agc_clk_divide bit name r/w reset description [7:0] agc_clock_divide r/w 40 agc clock divider for 2fsk/gfsk/msk/gmsk mode. the agc rate is (26 mhz/(16 agc_clk_divide)). table 114. 0x336: interrupt_source_0 bit name r/w reset description [7] interrupt_num_wakeups r/w 0 asserted when the number of wuc wake-ups (number_of_wakeups[15:0]) has reached the threshold (number_of_wakeups_irq_threshold[15:0]) [6] interrupt_swm_rssi_det r/w 0 asserted when the measured rssi during smart wake mode has exceeded the rssi threshold value (swm_rssi_thresh, address 0x108) [5] interrupt_aes_done r/w 0 asserted when an aes encryption or decryption command is complete; available only when the aes firmware module has been loaded to the adf7023-j program ram [4] interrupt_tx_eof r/w 0 asserted when a packet has finished transmitti ng (packet mode only) [3] interrupt_address_match r/w 0 asserted when a received packet has a valid address match (packet mode only) [2] interrupt_crc_correct r/w 0 asserted when a received packet has the correct crc (packet mode only) [1] interrupt_sync_detect r/w 0 asserted when a qualified sync word has been detected in the received packet [0] interrupt_preamble_detect r/w 0 asserted when a qualified preamble has been detected in the received packet table 115. 0x337: interrupt_source_1 bit name r/w reset description [7] battery_alarm r/w 0 battery voltage dr opped below the user-set threshold value [6] cmd_ready r/w 0 communications proc essor ready to accept a new command [5] unused r/w 0 [4] wuc_timeout r/w 0 wake-up timer has timed out [3] unused r/w 0 [2] unused r/w 0 [1] spi_ready r/w 0 spi ready for access [0] cmd_finished r/w 0 command has finished
adf7023-j rev. 0 | page 94 of 100 table 116. 0x338: calibration_control bit name r/w reset description [7:2] reserved r/w 0 [1] synth_cal_en r/w 0 1: enable the synthesizer calibration state machine 0: disable the synthesizer calibration state machine [0] rxbb_cal_en r/w 0 1: enable receiver baseband filter (rxbb) calibration 0: disable receiver baseband filter (rxbb) calibration table 117. 0x339: calibration_status bit name r/w reset description [7:3] reserved r 0 [2] pa_ramp_finished r 0 [1] synth_cal_ready r 0 1: synthesizer calibration finished successfully 0: synthesizer calibration in progress [0] rxbb_cal_ready r 0 receive if filter calibration 1: complete 0: in progress (valid while rxbb_cal_en = 1) table 118. 0x345: rxbb_cal_calwrd_readback bit name r/w reset description [5:0] rxbb_cal_calwrd r 0 rxbb reference oscillator calibration word; valid after rxbb calibration cycle has been completed. table 119. 0x346: rxbb_cal_calwrd_overwrite bit name r/w reset description [6:1] rxbb_cal_dcalwrd_ovwrt_in rw 0 rxbb refe rence oscillator calibration overwrite word [0] rxbb_cal_dcalwrd_ovwrt_en rw 0 1: enable rxbb reference oscillator calibration word overwrite mode 0: disable rxbb reference oscillator calibration word overwrite mode table 120. 0x359: adc_config_low bit name r/w reset description [7:4] reserved r/w 0 set to 0 [3:2] adc_ref_chsel r/w 0 0: rssi (default) 1: external ain 2: temperature sensor 3: unused [1:0] adc_reference_control r/w 0 the following reference values are valid for a 3 v supply: 0: 1.85 v (default) 1: 1.95 v 2: 1.75 v 3: 1.65 v table 121. 0x35a: adc_config_high bit name r/w reset description [7] reserved r/w 0 [6:5] filtered_adc_mode r/w 0 filtering modes 00: normal operation (no filter) 01: unfiltered agc loop, filter ed readback (updated upon mcr read) 10: unfiltered agc loop, filtered readback (update at agc clock rate) 11: filtered agc loop, filtered readback [4] adc_ext_ref_enb r/w 1 bring low to power down the adc reference [3:0] reserved r/w 1 set to 1
adf7023-j rev. 0 | page 95 of 100 table 122. 0x35c: agc_config bit name r/w reset description [7:6] lna_gain_change_order r/w 2 lna gain change order [5:4] mixer_gain_change_order r/w 1 mixer gain change order [3:2] filter_gain_change_order r/w 3 filter gain change order [1] allow_extra_lo_lna_gain r/w 0 allow extra low lna gain setting [0] disallow_max_gain r/w 0 disallow maximum agc gain setting table 123. 0x35d: agc_mode bit name r/w reset description [7] reserved r/w 0 [6:5] agc_operation_mcr r/w 0 0: free-running agc 1: manual agc 2: hold agc 3: lock agc after preamble [4:3] lna_gain r/w 0 0: low 1: medium 2: high 3: reserved [2] mixer_gain r/w 0 0: low 1: high [1:0] filter_gain r/w 0 0: low 1: medium 2: high 3: reserved table 124. 0x35e: agc_low_threshold bit name r/w reset description [7:0] agc_low_threshold r/w 55 agc low threshold table 125. 0x35f: agc_high_threshold bit name r/w reset description [7:0] agc_high_threshold r/w 105 agc high threshold table 126. 0x360: agc_gain_status bit name r/w reset description [7:5] reserved r 0 [4:3] lna_gain_readback r 0 0: low 1: medium 2: high 3: reserved [2] mixer_gain_readback r 0 0: low 1: high [1:0] filter_gain_readback r 0 0: low 1: medium 2: high 3: reserved table 127. 0x372: frequency_error_readback bit name r/w reset description [7:0] frequency_error_readback r 0 frequency error between received signal frequency and receive channel frequency = frequency_error_readback 1 khz. the frequency_error_readback value is in twos complement format.
adf7023-j rev. 0 | page 96 of 100 table 128. 0x3cb: vco_band_ovrw_val bit name r/w reset description [7:0] vco_band_ovrw_val r/w 0 overwrite value for the vco frequency band; active when vco_band_ovrw_en = 1. table 129. 0x3cc: vco_ampl_ovrw_val bit name r/w reset description [7:0] vco_ampl_ovrw_val r/w 0 overwrite value for the vco bias current dac; active when vco_ampl_ovrw_en= 1. table 130. 0x3cd: vco_ovrw_en bit name r/w reset description [7:6] reserved r/w 0 reserved. [5:2] vco_q_amp_ref r/w 0 vco amplitude level control reference dac during q phase [1] vco_ampl_ovrw_en r/w 0 1: enable vco bias current dac overwrite 0: disable vco bias current dac overwrite [0] vco_band_ovrw_en r/w 0 1: enable vco frequency band overwrite 0: disable vco frequency band overwrite table 131. 0x3d0: vco_cal_cfg bit name r/w reset description [7:4] reserved r/w 0 reserved. [3:0] vco_cal_cfg r/w 1 vco calibration state machine configuration. set vco_cal_cfg = 0xf to bypass vco calibration on the phy_tx and phy_rx transitions. set vco_cal_cfg = 0x1 to enable the vco calibrations on the transitions. table 132. 0x3d2: osc_config bit name r/w reset description [7:6] reserved r/w 0 write 0 [5:3] xosc_cap_dac r/w 0 26 mhz crystal oscillator (xosc26n) tuning capacitor control word [2:0] reserved r/w 0 write 0 table 133. 0x3da: vco_band_readback bit name r/w reset description [7:0] vco_band_readback r 0 readback of the vco bias current dac after calibration table 134. 0x3db: vco_ampl_readback bit name r/w reset description [7:0] vco_ampl_readback r 0 readback of the vco bias current dac after calibration table 135. 0x3f8: analog_test_bus bit name r/w reset description [7:0] analog_test_bus r/w 0 to enable analog rssi on atb3, set analog_test_bus = 0x64 in conjunction with setting rssi_tstmux_sel = 0x3. table 136. 0x3f9: rssi_tstmux_sel bit name r/w reset description [7] reserved r/w 0 [6:2] reserved r/w 0 [1:0] rssi_tstmux_sel r/w 0 to enable analog rssi on atb3, set rssi_tstmux_sel = 0x3 in conjunction with setting analog_test_bus = 0x64.
adf7023-j rev. 0 | page 97 of 100 table 137. 0x3fa: gpio_configure bit name r/w reset description [7:0] gpio_configure r/w 0 0x00: default 0x21: slicer output on gp5 (that is, bypass cdr) 0x40: limiter outputs on gp0(q) and gp1(i) 0x41: filtered limiter outputs on gp0(q) and gp1(i) and unfiltered limiter outputs on gp2(q) and irq_gp3 (i) 0x50: packet transmit data from communications processor on gp0 0x53: pa ramp finished on gp0 0xa0: sport mode 0 0xa1: sport mode 1 0xa2: sport mode 2 0xa3: sport mode 3 0xa4: sport mode 4 0xa5: sport mode 5 0xa6: sport mode 6 0xa7: sport mode 7 0xa8: sport mode 8 0xc9: test dac output on gp0 (also must set test_dac_gain) table 138. 0x3fd: test_dac_gain bit name r/w reset description [7:4] reserved r/w 0 reserved [3:0] test_dac_gain r/w 4 set test_dac_gain = 0 when using the test dac packet ram register description table 139. 0x00d: var_tx_mode var_tx_mode mode 0 default; no transmit test mode 1 reserved 2 transmit the preamble continuously 3 transmit the carrier continuously 4 to 255 reserved
adf7023-j rev. 0 | page 98 of 100 outline dimensions 033009-a 1 0.50 bsc bottom view top view pin 1 indicator 32 9 16 17 24 25 8 exposed pad p i n 1 i n d i c a t o r seating plane 0.05 max 0.02 nom 0.20 ref coplanarity 0.08 0.30 0.25 0.18 5.10 5.00 sq 4.90 0.80 0.75 0.70 for proper connection of the exposed pad, refer to the pin configuration and function descriptions section of this data sheet. 0.50 0.40 0.30 0.25 min 3.45 3.30 sq 3.15 compliant to jedec standards mo-220-whhd. figure 88. 32-lead lead frame chip scale package [lfcsp_wq] 5 mm 5 mm body, very very thin quad (cp-32-13) dimensions shown in millimeters ordering guide model 1 temperature range package description package option adf7023-jbcpz ?40c to +85c 32-lead lead frame chip scale package [lfcsp_wq] cp-32-13 adf7023-jbcpz-rl ?40c to +85c 32-lead lead frame chip scale package [lfcsp_wq] cp-32-13 eval-adf7xxxmb3z evaluation board (usb motherboard) EVAL-ADF7023-JDB1Z evaluation board (rf daughterboard, 950 mhz, separate match) eval-adf7023-jdb2z evaluation board (rf daughterboard, 950 mhz, combined match) 1 z = rohs compliant part.
adf7023-j rev. 0 | page 99 of 100 notes
adf7023-j rev. 0 | page 100 of 100 notes ?2011 analog devices, inc. all rights reserved. trademarks and registered trademarks are the property of their respective owners. d09555-0-5/11(0)

▲Up To Search▲

Price & Availability of EVAL-ADF7023-JDB1Z

	To Download EVAL-ADF7023-JDB1Z Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .